ASN 20 BR

From UG

(Difference between revisions)

Jump to: navigation, search

Revision as of 13:43, 18 September 2012

ASN 20 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
introduce some changes

General BR

ASN Portal

When communicating with / selling to prospective clients we use term "Portal".

ASN Portal "automates" segment or entire supply chain for given company.

Client specific MOTs

We need ability to name MOTs using language of particular client.

Example: for Arden in terms of MOT Domestic Trucking there would be the following MOT options defined:

Inbound Trucking - for all US/Canada moves
Other trucking - for any other truck domestic such as in Europe

Also, we would like to have two level hierarchy for MOT:

1st level called mode
2nd level called submode

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

Shipper and ASN form

Choice of mode for Shipper

Particular Shipper user should have options:

can not indicate MOT on ASN
can indicate just some MOTs

Commodity line splits

If Planner would like to approve smaller quantity then he will reject this ASN and Shipper needs to re-submit with smaller quantity.

For FCL offer Shipper to enter Container info

He should enter container info and link commodity lines to containers (optional).

If planner approves only partial ASN then drop this info.

Dims and CBM management

add choice to enter cbm or dims per line item vs per table

Planner and Approval process

Approval mode is not same for all ASNs

Approval mode is MOT / PO Issued By / Shipper specific.

Air Approval

This is an additional approval layer. Some Air ASNs needs to pass it before being finally approved. Some planner users have this right.

Misc

Flexible Shipments List

For every Shipment list (first of all for Shipper and Planner roles) user can define:

what columns are visible
order of columns

We like how it is implemented in Descartes.

ISA (Alex/Kostya):
----------------------------
* We should try to create "general solution", define superset of fields that can be re-used 
in various places in the system (internal also has CT List).
* Remember last configuration per user
* developer, pls review your implementation idea with Kostya

Merge Com and EQuery

Merge Com and E-Query and call it Com (for Client and Jag Ops roles)
Make new Com available to Shipper and Planner roles
Business reasons:
- functionality of Com and E-Query is almost identical
- user comments are spread across two threads - one in E-Query and another in Com which is inconvenient
- sometimes question is posted in E-Query and answer in Com which is inconvenient

ISA (Alex/Kostya/AK):
---------------------------
* Do not forget about such new linked to these components functionality as:
 * Pre-Alert Sent
 * Loss Authorized
* Please define well good migration path for existing data
* keep in mind that Master has Comments tab
* call it everywhere "Com"

Flag CT feature

For Shipper and Planner roles add ability to "flag" specific records
enable it on Shipments List page
"flagged" records should stand out (different background color, use orange)
we will also call it Watch List (but of course it is not same as Watch List as defined for Client Role)
NOTE: In the next version:
- notifications same as defined for current CT2 Client role Watch-list would be added
- "past due" email notifications (or dashboard) would be added

ISA (Alex/Kostya/AK/AG):
---------------------------------
* user should be able to select multiple records then then select "Flag/Watch" OR "Un-Flag"
* add filter to show only flagged records
* enable this for every tab 
* similar functionality exists in MS Outlook and Apple iPhoto

Add Create GRP action to Virtual Group

After ASN 20 is deployed more shipment will require grouping. Need additional mechanism to facilitate that.

ISA
-------------
Add one more action to Ops > Virtual Group component:
* create GRP

Add Clone User feature

We need to add Clone User feature.

It is required for this project because:

new Shipper profile has many options to set and therefore it is time-consuming
many shipper users will have similar profile
we do not have mechanism in place (yet) to set Shipper values for multiple users at one time due to absence of such entity as Shipper Company with users linked to it

Simultaneous access to record by Shippers Planners and 3PL users/system for update

Open access to ASN record for edit to Shippers, Planners and 3PL users/systems for update until Pick Up actual date is set.

Shippers and 3PLs might add info after Planner edited it.

Some rules still exists as far as what can be edited and when. See list below:

....
.....
.....

Add FTL vs LTL flag and add Truck table for FTL

FTL - full truck load. Paid per track regardless of weight/volume. For very large shipments.
LTL - less than truck load. Paid based on weight/volume. For small and medium shipments.

In ASN 2.0 we would like to request shipper to indicate what kind of shipment he is requesting.

Also this should be a sub-type of MOT offered to Shipper/Planner.

For FTL type of shipment we also would request truck related info - see below.

ISA 
---------------
Per Kostya the best way to implement is to add extra entity "Sub-mode" with values: {LTL, FTL}

Add Truck info

For FTL shipments need truck related info such as:

how many trucks of what sizes are required to move commodities defined on ASN

We want to request this info from Shippers when they submit ASN for FTL shipments.

Typical truck size values: 48 ft, 53 ft.

ISA
----------------------------
* manage truck sizes in Admin - add this as a tab to Admin > Transportation

IMPORTANT: If ASN is not approved completely first time by planner (all items) then clear Truck Info since it is relevant only if all commodities are moved together.

ASN transmit

Need option to automatically forward approved shipment info to another company (to handle transportation instead of Jag Ops).

Possibly need options:
- send as an xls attachment
- EDI/XML transfer
- other as defined by systems we interface with

Options to:
- auto send based on MOT/lanes
- manually send

Option to batch (send multiples in one transmission)

ISA (Alex):
--------------------------
* In this version I suggest to limit option to sending through e-mail 
with ASN info in attached xls. (one per ASN)

Preliminary demo to EA

IMPORTANT

Need to soon show core functionality to first prospective client - EA:

create ASN for Air / Ocean with typical Arden approval options

Due date: end of 1st or 2nd week of Oct.

To do list

Identify and list primary use cases that will be used for the demonstration.
Clarify truck table functionality with Shipper
Clarify container table functionality with Shipper

ASN Demo

ASN Demo in a nutshell

Create one portal
- add 2 po issued by
- add MOT synonyms: Air, Ocean/FCL, Ocean/LCL, Trucking
- add one transmit to non-Jag 3PL for one Air lane

Create one shipper
Create 2 planners for double approval process

Create 3 ASNs for various MOTs:
- one of them will be transmitted to non-Jag 3PL
- ASNs will have many commodity lines
- Planner will make full spectrum of various possible decision per commodity item:
  - approve
  - reject
  - hold

Demo Com functionality

More detailed use cases

TBD

@@ Line 93: / Line 93: @@
 === Merge Com and EQuery ===
-* Merge Com and E-Query and call it Com (for Client and Jag Ops role)
+* Merge Com and E-Query and call it Com (for Client and Jag Ops roles)
 * Make new Com available to Shipper and Planner roles
 * Business reasons:
@@ Line 100: / Line 100: @@
 ** sometimes question is posted in E-Query and answer in Com which is inconvenient
-  ISA (Alex/Kostya):
+  ISA (Alex/Kostya/AK):
   ---------------------------
   * Do not forget about such new linked to these components functionality as:
@@ Line 106: / Line 106: @@
    * Loss Authorized
   * Please define well good migration path for existing data
+ * keep in mind that Master has Comments tab
+ * call it everywhere "Com"
 === Flag CT feature ===