ASN 20 Requirements Bits

From UG

Contents 1 About 2 Core Needs 3 Shipper related 3.1 Domestic vs International shipments 3.2 Dom vs Inter Shippers 3.3 Case when one sniper ships under many supply chains 3.4 Approval type is Shipper specific 3.5 Supply chain vs E0 3.6 Shipper can or can not choose MOT 3.7 Truck MOTs for Shipper: LDP vs Domestic 3.8 If Shipper enters FCL then what type of FCL ? 3.9 Auto approval for Shippers 3.10 FCL mode for Shipper 3.11 List of additional fields on ASN Form 4 Planner related 4.1 Planner can change MOT 4.2 PO Issued By logic 5 Questions and Not Confirmed Requirements 6 August 20 changes 6.1 ASN workflow type 6.2 Add International Undefined ASN workflow 6.3 Transport mode and submode choices differ between Planners and Shippers for given ASN mode 6.4 System will create one CT for one ASN with multiple lines and present it to Planner 6.5 After Planner review System will create multiple CTs 6.6 Commodity line splits 6.7 Entering container info 6.8 Truck table for FTL

About

This wiki is a log of various selected requirements and design ideas SA collected from Product Team (Marc) prior to creating solution.

Due to limited time allocated the goal was not to create a doc to cover all requirements. Instead #ASN 20 Solution covers both solution and requirements.

Core Needs

ASN 20 will extend ASN 1.X to provide the following functionality - see below.

• extend Shipper / ASN / Planner / Jaguar Ops functionality to:
  • other MOTs (Air, Ocean, etc)
  • 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.

August 20 changes

ASN workflow type

We need to introduce new term: ASN workflow.

"ASN workflow" is a type of ASN logic associated with specific workflow.

This often is related to transport mode but does not have one to one correspondence.

Each "ASN workflow" has its own logic on a shipper, planner and Jag Ops level.

For example "Undefined International" ASN mode. See details below.

Add International Undefined ASN workflow

Add this workflow.

For this ASN mode Shipper will submit only commodity info and will not specify transportation mode or containers info.

Planner will have to define Transport Mode.

Transport Mode / Sub-mode choices presented to planner in this case:

• Ocean / LCL
• Ocean / FCL
• Air

[???] Do we need to present other choices such as trucking types?

Transport mode and submode choices differ between Planners and Shippers for given ASN mode

For example if CT has LDP mode assigned by Shipper portal will provide planners with a choice of mode.

(Also in this case planners cannot approve partial quantities I assume).

System will create one CT for one ASN with multiple lines and present it to Planner

Exception: EA DOM PORTAL. Do we really want to have a separate logic for "Truck Dom with TMS" ASN mode?

After Planner review System will create multiple CTs

Planner will make separate decision for every commodity line.

System will group lines with same approval status (approve, reject, hold, no decision).

NOTE: "no decision" could happen if this is subject for review by another Planner.

For approved lines this CT will be re-used and forwarded to Jag Ops.

For each group out of (reject, hold, no decision) group separate new CT will be created.

What will happen in FCL case. What will happen with containers table?

Commodity line splits

If Planner would like to approve smaller quantity then system will create CT with rejected status notifying Shipper that he needs to re-submit. This is to be confirmed by Simon.

Entering container info

In some cases Shipper will be required to enter container info.

To enter this info container table will be provided.

Shipper is not required to link specific commodity to specific container. Will this create a problem when this CT propagates to Jag Ops?

Truck table for FTL

For FTL I suggest introducing truck table similar to container table.