ASN 20 Requirements Bits

From UG

Revision as of 22:25, 10 August 2012 by Alex (Talk | contribs)
Jump to: navigation, search


Contents

Core Needs

  • extend Shipper / Planner / ASN functionality to:
    • other MOTs for Arden (Air, Ocean, etc)
    • extend all ASN functionality to any Client Company
  • add some additional features (such as Additional MOT Air approval)
  • introduce some changes (such as FTL/LTL logic)

Shipper related

Domestic vs International shipments

  • Def: USA Domestic EA shipments - EA shipments from one point to another within US/Canada. TMS is used to manage these.
  • Def: International EA shipments - EA shipments from one continent to another. Each shipments represents the following chain:
    • export trucking segment (origin door to port)-> Air (port to port) -> import trucking segment (port to destin door)
    • export trucking segment (origin door to port)-> Ocean (port to port) -> import trucking segment (port to destin door)

Dom vs Inter Shippers

  • EA Shippers can be divided into categories:
    • create/view only USA Domestic shipments
    • create/view only International shipments
    • create/view both


Case when one sniper ships under many supply chains

  • Consider case when one shipper serves >1 client company. Per Marc's vision Shipper should access/manage shipments for different E0 separately. If CEI as a Shipper ships "under" Coty and EA supply chains then CEI shipper user will have two links or two items in a single drop down to switch from managing Coty vs EA shipments. (Marc strongly believes we should not mix CTs from different Clients)

Approval type is Shipper specific

  • "Approval type" for specific mode (auto vs basic/super, etc) - is it a property of Client Company/PO Issued By/Shipper/MOT combination.

Supply chain vs E0

  • Supply chain is defined / associated with Client Company E0.

Shipper can or can not choose MOT

  • Shipper profile should have 2 options:
    • Shipper can choose Air or Ocean
    • Shipper can not

In 2nd case he needs to enter info in the form "ready for FCL" (if it is FCL type in case of ocean)

Truck MOTs for Shipper: LDP vs Domestic

Shippers will have the following options to choose from for Truck related moves:

  • LDP FCL - corresponds to Truck Ocean
  • LDP LCL - corresponds to Truck Ocean
  • LDP Air - corresponds to Truck Air
  • Domestic - corresponds to Truck Domestic (TMS and non TMS options are regulated through Client Company profile)

LDP will not be managed through TMS.

Normally LCL corresponds to LTL and FCL to FTL.

Shipper's USA office or overseas office will enter ASN.

If Shipper enters FCL then what type of FCL ?

Shipper can not decide MLB vs AW (submode). Operator needs to make this decision.

Same situation is for LCL vs Client Consol.

Possible solution:

  • Let Shipper select btw FCL and LCL
  • Report for jag on FCL vs LCL (DB Rep)
  • Jag Op will open CT and see it as MOT=Undefined but with indication of Shippers MOT (FCL vs LCL).
  • Then Jag Op will set "submode"

Auto approval for Shippers

Some Shippers will have auto approval just for Air some just for Ocean.

FCL mode for Shipper

Shipper should choose between FCL and LCL. In case he selected FCL then:

  • he must define commodity per container
  • he must define commodity for each container in one line
  • he must indicate type/size of container

List of additional fields on ASN Form

  • MOT single select
  • for FCL or LDP FCL:
    • cont size single select
    • cont type single select
    • and NOTE: define commodities for each container in ONE line only
  • for FTL:
    • truck size single select
    • and NOTE: define commodities for each truck in ONE line only

Planner related

Planner can change MOT

Yes.

PO Issued By logic

  • "PO issued by" logic will remain. PO issued by list will be complemented by several more items to cover International moves. This is how we define what planner manages what CTs (Shipper sets PO issued by tag on CT and Planner profile has a list of PO issued by values).

Questions and Not Confirmed Requirements

  • PU and Del location single selects on ASN form. Obviously should not show all options avail in CT2. Logic/Solution TBD.

Requirements not satisfied with reasons

  • Req: Rename "Shipper" link on Client to "ASN Portal"
    • we believe that it will confuse existing EA DOM users
  • Req: On Client profile change from checkbox to Y / N radio
    • do not see compelling reason to change existing approach
Retrieved from "https://wiki.jaguarfreight.com/ASN_20_Requirements_Bits"
Personal tools