ASN 20 Requirements Bits

From UG

(Difference between revisions)
Jump to: navigation, search
(→Core Needs)
Line 10: Line 10:
* introduce some changes (such as FTL/LTL logic)
* introduce some changes (such as FTL/LTL logic)
 +
 +
== Scope change: ASN 2.0 vs International Portal and related gaps ==
 +
 +
Original scope for International Portal was changed and this reduced scope to be called ASN 2,0 since there is a need to push into Prod some features. This name hints that most features are related to ASN functionality.
 +
 +
Some features that were developed or half-developed such as Flex CT editor, merge of Client and Internal App were put on hold.
 +
 +
Some such as Flex User roles will be used, but some adjustment required (some Roles will be Flexible and some Built In=Hardcoded).
 +
 +
Key open question is: do we need to separate ASN 2.0 Generic Sipper/Planner Roles and ASN 2.0 EA Sipper/Planner Roles. Ideally not.
 +
 +
Also we need to provide TMS vs non TMS option for Truck domestic. It should be Client company specific.
=== Domestic vs International shipments ===
=== Domestic vs International shipments ===

Revision as of 22:52, 25 July 2012


Contents

Core Needs

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

Scope change: ASN 2.0 vs International Portal and related gaps

Original scope for International Portal was changed and this reduced scope to be called ASN 2,0 since there is a need to push into Prod some features. This name hints that most features are related to ASN functionality.

Some features that were developed or half-developed such as Flex CT editor, merge of Client and Internal App were put on hold.

Some such as Flex User roles will be used, but some adjustment required (some Roles will be Flexible and some Built In=Hardcoded).

Key open question is: do we need to separate ASN 2.0 Generic Sipper/Planner Roles and ASN 2.0 EA Sipper/Planner Roles. Ideally not.

Also we need to provide TMS vs non TMS option for Truck domestic. It should be Client company specific.

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

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).

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.

Approval type is Shipper specific

  • "Approval type" for specific mode (auto vs basic/super, etc) - is it a property of Client Company/Shipper 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

Planner can change MOT

Change between Air, FCL, LCL. Correct?

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

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.
Retrieved from "https://wiki.jaguarfreight.com/ASN_20_Requirements_Bits"
Personal tools