ASN 20 Requirements Bits

From UG

(Difference between revisions)
Jump to: navigation, search
 
(59 intermediate revisions not shown)
Line 1: Line 1:
-
[[Category:IP2]]
+
[[Category:ASN 20]]
-
== Misc R ==
+
== About ==
 +
 
 +
This wiki is a log of various selected requirements and design ideas SA collected from Product Team (Marc) prior to creating solution.
 +
 
 +
== 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: USA Domestic EA shipments - EA shipments from one point to another within US/Canada. TMS is used to manage these.
Line 8: Line 14:
** 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)-> 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)
** 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:
* EA Shippers can be divided into categories:
Line 14: Line 22:
** create/view both
** create/view both
-
* "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).
 
-
* 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.
+
=== Case when one sniper ships under many supply chains ===
-
* "Approval type" for specific mode (auto vs basic/super, etc) - is it a property of Client Company/Shipper combination.
+
* 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.
* Supply chain is defined / associated with Client Company E0.
Line 38: Line 51:
* LDP Air - corresponds to Truck Air
* LDP Air - corresponds to Truck Air
* Domestic - corresponds to Truck Domestic (TMS and non TMS options are regulated through Client Company profile)
* 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 ? ===
=== If Shipper enters FCL then what type of FCL ? ===
Line 61: Line 80:
* he must define commodity for each container in one line
* he must define commodity for each container in one line
* he must indicate type/size of container
* he must indicate type/size of container
-
 
-
=== Planner can change MOT ===
 
-
 
-
Change between Air, FCL, LCL. Correct?
 
=== List of additional fields on ASN Form ===
=== List of additional fields on ASN Form ===
Line 78: Line 93:
** truck size single select
** truck size single select
** and NOTE: define commodities for each truck in ONE line only
** and NOTE: define commodities for each truck in ONE line only
 +
 +
== Planner related ==
 +
 +
=== Planner can change MOT ===
 +
 +
Yes.
== Questions and Not Confirmed Requirements ==
== 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.
* PU and Del location single selects on ASN form. Obviously should not show all options avail in CT2. Logic/Solution TBD.
 +
 +
== August 20 changes ==
 +
 +
=== Container and Truck Info management on Shipper and Planner level ===
 +
 +
* add option for Shipper to enter this info
 +
* what to do if not all line items are approved?
 +
** Simon suggested Warning and erase
 +
 +
=== Partial QTY approval ===
 +
 +
Reject this line item with warning.
 +
 +
=== Planner will take separate action on each ASN line item as far as Approval type and MOT ===
 +
 +
Simon/Marc suggested below.
 +
 +
After planner decided on (per line item) what approval type and MOT are:
 +
 +
Create unique groups as far as approval/MOT combination.
 +
 +
For each create CT.
 +
 +
Re-use CT that was created from ASN for CT with approved items/MOT with earliest in sorted alphabetically list.
 +
 +
=== Make most of commod table fields optional ===
 +
 +
Regulate what fields to hide or show in admin.
 +
 +
<??? on  what level? E0 or Portal?  ???>
 +
 +
=== ASN workflow class ===
 +
 +
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 class. See details below.
 +
 +
=== Add International Undefined ASN workflow class ===
 +
 +
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. <font color="red">Do we really want to have a separate logic for "Truck Dom with TMS" ASN mode?
 +
</font>
 +
 +
=== 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.
 +
 +
<font color="red">What will happen in FCL case. What will happen with containers table?</font>
 +
 +
=== 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. <font color="red">Will this create a problem when this CT propagates to Jag Ops? </font>
 +
 +
=== Most of other client companies will have very simple workflow ===
 +
 +
* auto-approval
 +
*
 +
 +
=== Trucking MOT re-design ===
 +
 +
Per Simon/Marc:
 +
 +
* For FTL need to introduce truck table similar to container table. Fields:
 +
** seal #
 +
** trailer #
 +
** size
 +
 +
* One CT can be mapped to multiple trucks.
 +
 +
* Re factor existing related fields / code:
 +
** PT/DT number field
 +
** reports and other code that use PT/DT currently
 +
 +
* Create for both pick up and delivery trucker
 +
 +
* This should work identically on internal and Client (ASN) App
 +
 +
* This is to be associated with "Truck Domestic" MOT
 +
 +
<i> <<< ???
 +
 +
Challenges:
 +
 +
* We need to create one design that would satisfy:
 +
** generic Truck Domestic case (any client, any country/continent)
 +
** "TMS based" trucking that have TMS limitations - see below (now used by E0= EA DOM PORTAL)
 +
 +
* Can we relax limitations below?
 +
 +
* Can in general case one CT contain commodities that would be moved on different trucks (and possibly different times)?
 +
** for TMS based of course this is not possible
 +
 +
Need to consider limitation of TMS:
 +
* a) there is a max on # of palets which is equiv to 1 truck
 +
* b) number of commod lines for CTs that are sent to TMS can not be > 1 (can we lift that restriction?)
 +
** possible solution is to "split CTs" before sending to TMS
 +
 +
* KEY QUESTION: We will need to tag each CT as FTL or LTL. What is the meaning of CT having MOT = FTL vs LTL  (and FCL vs LCL):
 +
** If has MOT=FTL then it means that:
 +
*** a) all contents are shipped on one truck
 +
*** b) that truck has nothing else except that CT
 +
*** c) that truck is nearly full as far as its capacity
 +
*** d) rates that are applied are FTL rates
 +
** OR If has MOT=FTL then it means that:
 +
*** a) all contents of these CT are shipped on one truck (together CTs) - it is part of "FCL group"
 +
*** b) that truck has other CTs but only from particular "FCL group"
 +
*** c) that truck is nearly full as far as its capacity
 +
*** d) rates that are applied are FTL rates
 +
* OR it is only indicates what type of rates are used?
 +
 +
New design has to take into account:
 +
 +
* we already collect info for 2 types of trucking segments:
 +
** "pick up" trucking
 +
** "delivery" trucking
 +
 +
Also:
 +
 +
* we already have two fields for trailer #s:
 +
** [[CT#PT_Number]] - PU trailer id
 +
** [[CT#DT_Number]] - Deliv trailer id
 +
 +
Do we re- use these fields and How?
 +
 +
ASN related:
 +
 +
Possible solution:
 +
* to give choice to shipper to enter per truck or just commodity table. (ask them to "form" trucks)
 +
* questions:
 +
** what if they "create" trucks that are not full or half full or even almost empty?
 +
What is the value?
 +
** if planners anyways will approve only some lines making these trucks half empty what is the value of asking Shippers to "form/create trucks"
 +
 +
Other questions:
 +
* Simon suggested that Shippers might know trailer# and seal#. It is not clear how would they know this info so far in advance.
 +
 +
???>>>
 +
</i>
 +
 +
==== Trucking MOT re-design Possible Solution One ====
 +
 +
[[File:Truck table.png]]
 +
 +
Assumptions:
 +
 +
* we create one design for all cases of MOT="Truck Domestic":
 +
** TMS based
 +
** North America non TMS such as Hanover
 +
** Europe, Asia, etc
 +
 +
* commodities to truck mapping; FCL vs LCL:
 +
** each CT has commodities defined equivalent to one truck or less
 +
** commodities assigned to one CT will travel together from Origin door to Destination in many cases together with commodities from other CTs. Another-words it is not possible that one line of commode table will travel on one truck and another on another truck.
 +
** we want to add sub-mode field. Values: FCL, LCL. This will indicate what type of tariffs is used. Also it would mean that if CT is tagged as LCL then commodities from this CT are traveling together with commodities from other CTs.
 +
 +
* truck info, legs, etc:
 +
** LCL:
 +
*** we assume that only ONE truck company handles move
 +
*** we do not collect truck info such as seal/trailer id
 +
** FCL has 2 cases:
 +
*** one leg trip:  only one truck company is used; we collect truck seal/trailer id;
 +
*** two legs with Pool Point: possibly two truck companies/trucks are used; we collect truck seal/trailer id for both;
 +
 +
=== Records list for Shipper: show commodity lines or not ===
 +
 +
Provide choice.
 +
 +
=== Jag Ops DR rep ===
 +
 +
* Show only counter for Approved but not Actioned
 +
* remove "routed"
 +
* add extra column "approved and not actioned over X days"
 +
* Add link to Virt group from other DR reps
 +
 +
=== Shipments list ===
 +
 +
* do not show submode
 +
* add "any" to mode filter
 +
 +
=== Assign commod. lines to container table on ASN form or not ===
 +
 +
Make it Portal properties.
 +
 +
=== Post Approval Shippers update ===
 +
 +
* update container/trucker table
 +
 +
== Sept 7 ==
 +
 +
Created [[ASN 20 BRBA]]

Current revision as of 23:45, 2 August 2013


Contents

[edit] About

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

[edit] Shipper related

[edit] 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)

[edit] 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


[edit] 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)

[edit] 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.

[edit] Supply chain vs E0

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

[edit] 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)

[edit] 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.

[edit] 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"

[edit] Auto approval for Shippers

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

[edit] 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

[edit] 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

[edit] Planner related

[edit] Planner can change MOT

Yes.

[edit] 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.

[edit] August 20 changes

[edit] Container and Truck Info management on Shipper and Planner level

  • add option for Shipper to enter this info
  • what to do if not all line items are approved?
    • Simon suggested Warning and erase

[edit] Partial QTY approval

Reject this line item with warning.

[edit] Planner will take separate action on each ASN line item as far as Approval type and MOT

Simon/Marc suggested below.

After planner decided on (per line item) what approval type and MOT are:

Create unique groups as far as approval/MOT combination.

For each create CT.

Re-use CT that was created from ASN for CT with approved items/MOT with earliest in sorted alphabetically list.

[edit] Make most of commod table fields optional

Regulate what fields to hide or show in admin.

<??? on what level? E0 or Portal?  ???>

[edit] ASN workflow class

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 class. See details below.

[edit] Add International Undefined ASN workflow class

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?

[edit] 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).

[edit] 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?

[edit] 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?

[edit] 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?

[edit] Most of other client companies will have very simple workflow

  • auto-approval

[edit] Trucking MOT re-design

Per Simon/Marc:

  • For FTL need to introduce truck table similar to container table. Fields:
    • seal #
    • trailer #
    • size
  • One CT can be mapped to multiple trucks.
  • Re factor existing related fields / code:
    • PT/DT number field
    • reports and other code that use PT/DT currently
  • Create for both pick up and delivery trucker
  • This should work identically on internal and Client (ASN) App
  • This is to be associated with "Truck Domestic" MOT

<<< ???

Challenges:

  • We need to create one design that would satisfy:
    • generic Truck Domestic case (any client, any country/continent)
    • "TMS based" trucking that have TMS limitations - see below (now used by E0= EA DOM PORTAL)
  • Can we relax limitations below?
  • Can in general case one CT contain commodities that would be moved on different trucks (and possibly different times)?
    • for TMS based of course this is not possible

Need to consider limitation of TMS:

  • a) there is a max on # of palets which is equiv to 1 truck
  • b) number of commod lines for CTs that are sent to TMS can not be > 1 (can we lift that restriction?)
    • possible solution is to "split CTs" before sending to TMS
  • KEY QUESTION: We will need to tag each CT as FTL or LTL. What is the meaning of CT having MOT = FTL vs LTL (and FCL vs LCL):
    • If has MOT=FTL then it means that:
      • a) all contents are shipped on one truck
      • b) that truck has nothing else except that CT
      • c) that truck is nearly full as far as its capacity
      • d) rates that are applied are FTL rates
    • OR If has MOT=FTL then it means that:
      • a) all contents of these CT are shipped on one truck (together CTs) - it is part of "FCL group"
      • b) that truck has other CTs but only from particular "FCL group"
      • c) that truck is nearly full as far as its capacity
      • d) rates that are applied are FTL rates
  • OR it is only indicates what type of rates are used?

New design has to take into account:

  • we already collect info for 2 types of trucking segments:
    • "pick up" trucking
    • "delivery" trucking

Also:

Do we re- use these fields and How?

ASN related:

Possible solution:

  • to give choice to shipper to enter per truck or just commodity table. (ask them to "form" trucks)
  • questions:
    • what if they "create" trucks that are not full or half full or even almost empty?

What is the value?

    • if planners anyways will approve only some lines making these trucks half empty what is the value of asking Shippers to "form/create trucks"

Other questions:

  • Simon suggested that Shippers might know trailer# and seal#. It is not clear how would they know this info so far in advance.

???>>>

[edit] Trucking MOT re-design Possible Solution One

File:Truck table.png

Assumptions:

  • we create one design for all cases of MOT="Truck Domestic":
    • TMS based
    • North America non TMS such as Hanover
    • Europe, Asia, etc
  • commodities to truck mapping; FCL vs LCL:
    • each CT has commodities defined equivalent to one truck or less
    • commodities assigned to one CT will travel together from Origin door to Destination in many cases together with commodities from other CTs. Another-words it is not possible that one line of commode table will travel on one truck and another on another truck.
    • we want to add sub-mode field. Values: FCL, LCL. This will indicate what type of tariffs is used. Also it would mean that if CT is tagged as LCL then commodities from this CT are traveling together with commodities from other CTs.
  • truck info, legs, etc:
    • LCL:
      • we assume that only ONE truck company handles move
      • we do not collect truck info such as seal/trailer id
    • FCL has 2 cases:
      • one leg trip: only one truck company is used; we collect truck seal/trailer id;
      • two legs with Pool Point: possibly two truck companies/trucks are used; we collect truck seal/trailer id for both;

[edit] Records list for Shipper: show commodity lines or not

Provide choice.

[edit] Jag Ops DR rep

  • Show only counter for Approved but not Actioned
  • remove "routed"
  • add extra column "approved and not actioned over X days"
  • Add link to Virt group from other DR reps

[edit] Shipments list

  • do not show submode
  • add "any" to mode filter

[edit] Assign commod. lines to container table on ASN form or not

Make it Portal properties.

[edit] Post Approval Shippers update

  • update container/trucker table

[edit] Sept 7

Created ASN 20 BRBA

Retrieved from "https://wiki.jaguarfreight.com/ASN_20_Requirements_Bits"
Personal tools