ASN 20 BR

From UG

(Difference between revisions)
Jump to: navigation, search
(→Client specific MOTs)
(→Config)
 
(49 intermediate revisions not shown)
Line 12: Line 12:
* introduce some changes
* introduce some changes
-
== General BRBA ==
+
== General BR ==
=== ASN Portal ===
=== ASN Portal ===
Line 49: Line 49:
=== Commodity line splits ===
=== 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.  
+
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 ===
=== For FCL offer Shipper to enter Container info ===
-
He should enter container info and link commodity lines to containers (optional).
+
Simply allow shipper to indicate how many containers of what size/type are required to move this shipment.
-
 
+
-
If planner approves only partial ASN then drop this info.
+
-
 
+
=== Dims and CBM management ===
=== Dims and CBM management ===
Line 76: Line 72:
== Misc ==
== Misc ==
-
=== Simultaneous access to record by Shippers Planners and 3PL users/system for update ===
+
=== Flexible Shipments List ===
-
Open access to ASN record for edit to Shippers, Planners and 3PL users/systems for update until Pick Up actual date is set.
+
For every Shipment list (first of all for Shipper and Planner roles) user can define:
-
Shippers and 3PLs might add info after Planner edited it.
+
* what columns are visible
 +
* order of columns
-
Some rules still exists as far as what can be edited and when. See list below:
+
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
-
=== Add FTL vs LTL flag ===
+
=== Merge Com and EQuery ===
-
* FTL - full truck load. Paid per track regardless of weight/volume. For very large shipments.
+
* Merge Com and E-Query and call it Com (for Client and Jag Ops roles)
-
* LTL - less than truck load. Paid based on weight/volume. For small and medium shipments.
+
* 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
-
In ASN 2.0 we would like to request shipper to indicate what kind of shipment he is requesting.
+
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"
-
Also this should be a sub-type of MOT offered to Shipper/Planner.
+
=== Flag CT feature ===
-
For FTL type of shipment we also would request truck related info - see [[#Add Truck info]].
+
* 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
-
=== Add Truck info ===
 
-
For FTL shipments need truck related info such as:
+
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
-
* truck size
+
=== Add Create GRP action to Virtual Group  ===
-
* trailer id
+
-
* seal number
+
-
* ability to map commodity items to particular truck
+
-
We want to request this info from Shippers when they submit ASN for FTL shipments.
+
After ASN 20 is deployed more shipment will require grouping. Need additional mechanism to facilitate that.
-
Typical truck size values: 48 ft, 53 ft.
+
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 ===
=== ASN transmit ===
=== ASN transmit ===
 +
<div style="background-color:lightSteelBlue">
* Need option to automatically forward approved shipment info to another company (to handle transportation instead of Jag Ops).  
* Need option to automatically forward approved shipment info to another company (to handle transportation instead of Jag Ops).  
Line 126: Line 171:
* Option to batch (send multiples in one transmission)
* 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)
 +
</div>
=== Preliminary demo to EA ===
=== Preliminary demo to EA ===
Line 136: Line 187:
Due date: end of 1st or 2nd week of Oct.
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
 +
 +
=== ASN Demo in details  ===
 +
 +
==== Business Story ====
 +
 +
Apple hired Jaguar to:
 +
* provide ASN software system to manage ASN/planning process for one of its new product lines
 +
* provide 3PL services for some of its shipping lanes
 +
 +
Supply/Transportation Chain consists of the following three segments:
 +
* Air: USA to Russia
 +
* Ocean: USA to Asia
 +
* Trucking: USA to Canada
 +
 +
Planning:
 +
* each destination country/region is issuing its own PO:
 +
** Apple Russia
 +
** Apple Asia
 +
** Apple Canada
 +
* there are two planners: one basic and one super (for Air only)
 +
* double approval is required for Air, Single - for Ocean and Auto for Trucking.
 +
 +
They employ one subcontractor company in India IndiBPO that enters all ASNs into the system.
 +
 +
3PL services:
 +
* USA to Russia Air is handled by Belomor freight forwarder
 +
** they do not have too many of such shipments so best solution is to send them ASNs by email in attachment
 +
* Ocean and Trucking lanes by Jaguar
 +
 +
==== Config ====
 +
 +
'''Prerequisites:'''
 +
 +
* Create Client Company with name:
 +
* AppleASN
 +
* Create one ASN Transmit option with parameters:
 +
** Belomor (3PL), User Defined, e-mail, planner@belomor.com
 +
 +
'''Create one portal:'''
 +
 +
Portal parameters - General:
 +
* Name = Apple
 +
* Related E0 = Apple1
 +
 +
MOT tab parameters:
 +
* Air, n/a, Air, country:USA, country: Russia, Belomor(3PL), n/a
 +
* Ocean, FCL, Ocean FCL(AW), country: USA, region: Asia, Jaguar CT2, Apple1
 +
* Ocean, LCL, Ocean LCL, country: USA, region: Asia, Jaguar CT2, Apple1
 +
* Trucking Domestic, Truck, n/a, country: USA, country: Canada, Jaguar CT2, Apple1
 +
 +
'''Approval Tab:'''
 +
* Select second radio option (to enable Approval process)
 +
*  add 2 PO issued by: (no SKU map)
 +
** Apple Eurasia
 +
** Apple Canada
 +
 +
Approval modes:
 +
* Air, double, double
 +
* Ocean, FCL, single, single, single
 +
* Ocean, LCL, single, single, single
 +
* Trucking Domestic, auto, auto, auto
 +
 +
For both PO Issued by:
 +
* AirApproval = N
 +
* Cargo due date = Y
 +
 +
'''Create one shipper:'''
 +
 +
* Create user john@indibpo.com with Generic Shipper role
 +
* link to Apple portal
 +
* leave all defaults from Portal settings
 +
* define that Shipper can select all modes/submodes
 +
 +
'''Create one basic planner and one super planner:'''
 +
 +
Basic:
 +
* Create user basicplanner@apple.com with Generic Planner role
 +
* In Role section:
 +
** link to Apple portal
 +
** select all PO Issued By
 +
 +
Super:
 +
* Create user basicplanner@apple.com with Generic Planner role
 +
* in Role section:
 +
** link to Apple portal
 +
** select only Apple Russia PO Issued By
 +
** set as "Super Planner"
 +
 +
==== Demo Misc functionality ====
 +
 +
'''Demo Com'''
 +
 +
* Create Jag operator user oper@jaguarfreight.com
 +
* let shipper post note/e-mail to planner in given CT
 +
* let planner post note/e-mail to jag oper
 +
* let jag ops reply to comment above
 +
* show that all messages above form trail under Com section in that CT
 +
 +
'''Demo dims'''
 +
 +
'''Demo FCL containers feature'''
 +
 +
==== Demo ASN submission/approval ====
 +
 +
CT#1:
 +
* shipper creates Air: USA to Russia
 +
* basic planner approves
 +
* super planner approves
 +
* system transmits to 3rd party 3PL (Belomor)
 +
 +
CT#2:
 +
* shipper creates Ocean LCL: USA to Asia
 +
* basic planner:
 +
** approves some commodities with original mode/submode
 +
** approves some commodities with another mode/submode: Ocean FCL
 +
** rejects some
 +
** puts some on hold
 +
 +
CT#3:
 +
* shipper creates Trucking: USA to Canada
 +
* shipment is auto approved
 +
 +
Demonstrate:
 +
* how system creates CTs.
 +
* new features of Shipment list:
 +
** filters
 +
** search
 +
 +
=== SOWs that cover demo ===
 +
 +
"*" - tasks that '''must''' be completed before demo
 +
 +
11.1 SOW 1 Create new branch for this project from trunk; create envir for QA/SIT/UAT
 +
11.2 SOW 2 Add Clone User feature
 +
11.3 SOW 3 Misc: Add Create GRP action to Virtual Group
 +
11.4 SOW 4 Create and consolidate TMS and ASN Admins
 +
11.5 SOW 8 Re-design SKU Map
 +
11.6 SOW 7 Flag CT feature
 +
* 11.7 SOW 5 Merge Com and EQuery
 +
* 11.8 SOW 6 Flexible Shipments List
 +
11.9 SOW 9 Add TMS E0 attribute
 +
11.10 SOW 10 Tune Role Admin
 +
* 11.11 SOW 11 New Planner Profile
 +
* 11.12 SOW 12 Shipments List for a Planner user
 +
* 11.13 SOW 13 Approval related logic
 +
* 11.14 SOW 14 Add FTL vs LTL flag and add Truck table for FTL
 +
* 11.15 SOW 15 ASN transmit
 +
11.16 SOW 16 ANA report
 +
11.17 SOW 17 Jaguar Misc functionality
 +
* 11.18 SOW 18 List of Portals and Portal Profile
 +
* 11.19 SOW 19 New Shipper Profile
 +
* 11.20 SOW 20 New ASN Form
 +
* 11.21 SOW 21 Shipments List for a Shipper user

Current revision as of 16:43, 11 October 2012


Contents

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

[edit] General BR

[edit] ASN Portal

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

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

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

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

[edit] Shipper and ASN form

[edit] Choice of mode for Shipper

Particular Shipper user should have options:

  • can not indicate MOT on ASN
  • can indicate just some MOTs

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

[edit] For FCL offer Shipper to enter Container info

Simply allow shipper to indicate how many containers of what size/type are required to move this shipment.

[edit] Dims and CBM management

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

[edit] Planner and Approval process

[edit] Approval mode is not same for all ASNs

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

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


[edit] Misc

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

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

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

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

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

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

  • ....
  • .....
  • .....

[edit] Add FTL vs LTL flag and add Truck table for FTL

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

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

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

[edit] ASN Demo

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

[edit] ASN Demo in details

[edit] Business Story

Apple hired Jaguar to:

  • provide ASN software system to manage ASN/planning process for one of its new product lines
  • provide 3PL services for some of its shipping lanes

Supply/Transportation Chain consists of the following three segments:

  • Air: USA to Russia
  • Ocean: USA to Asia
  • Trucking: USA to Canada

Planning:

  • each destination country/region is issuing its own PO:
    • Apple Russia
    • Apple Asia
    • Apple Canada
  • there are two planners: one basic and one super (for Air only)
  • double approval is required for Air, Single - for Ocean and Auto for Trucking.

They employ one subcontractor company in India IndiBPO that enters all ASNs into the system.

3PL services:

  • USA to Russia Air is handled by Belomor freight forwarder
    • they do not have too many of such shipments so best solution is to send them ASNs by email in attachment
  • Ocean and Trucking lanes by Jaguar

[edit] Config

Prerequisites:

  • Create Client Company with name:
  • AppleASN
  • Create one ASN Transmit option with parameters:
    • Belomor (3PL), User Defined, e-mail, planner@belomor.com

Create one portal:

Portal parameters - General:

  • Name = Apple
  • Related E0 = Apple1

MOT tab parameters:

  • Air, n/a, Air, country:USA, country: Russia, Belomor(3PL), n/a
  • Ocean, FCL, Ocean FCL(AW), country: USA, region: Asia, Jaguar CT2, Apple1
  • Ocean, LCL, Ocean LCL, country: USA, region: Asia, Jaguar CT2, Apple1
  • Trucking Domestic, Truck, n/a, country: USA, country: Canada, Jaguar CT2, Apple1

Approval Tab:

  • Select second radio option (to enable Approval process)
  • add 2 PO issued by: (no SKU map)
    • Apple Eurasia
    • Apple Canada

Approval modes:

  • Air, double, double
  • Ocean, FCL, single, single, single
  • Ocean, LCL, single, single, single
  • Trucking Domestic, auto, auto, auto

For both PO Issued by:

  • AirApproval = N
  • Cargo due date = Y

Create one shipper:

  • Create user john@indibpo.com with Generic Shipper role
  • link to Apple portal
  • leave all defaults from Portal settings
  • define that Shipper can select all modes/submodes

Create one basic planner and one super planner:

Basic:

  • Create user basicplanner@apple.com with Generic Planner role
  • In Role section:
    • link to Apple portal
    • select all PO Issued By

Super:

  • Create user basicplanner@apple.com with Generic Planner role
  • in Role section:
    • link to Apple portal
    • select only Apple Russia PO Issued By
    • set as "Super Planner"

[edit] Demo Misc functionality

Demo Com

  • Create Jag operator user oper@jaguarfreight.com
  • let shipper post note/e-mail to planner in given CT
  • let planner post note/e-mail to jag oper
  • let jag ops reply to comment above
  • show that all messages above form trail under Com section in that CT

Demo dims

Demo FCL containers feature

[edit] Demo ASN submission/approval

CT#1:

  • shipper creates Air: USA to Russia
  • basic planner approves
  • super planner approves
  • system transmits to 3rd party 3PL (Belomor)

CT#2:

  • shipper creates Ocean LCL: USA to Asia
  • basic planner:
    • approves some commodities with original mode/submode
    • approves some commodities with another mode/submode: Ocean FCL
    • rejects some
    • puts some on hold

CT#3:

  • shipper creates Trucking: USA to Canada
  • shipment is auto approved

Demonstrate:

  • how system creates CTs.
  • new features of Shipment list:
    • filters
    • search

[edit] SOWs that cover demo

"*" - tasks that must be completed before demo 

11.1 SOW 1 Create new branch for this project from trunk; create envir for QA/SIT/UAT 
11.2 SOW 2 Add Clone User feature 
11.3 SOW 3 Misc: Add Create GRP action to Virtual Group
11.4 SOW 4 Create and consolidate TMS and ASN Admins
11.5 SOW 8 Re-design SKU Map
11.6 SOW 7 Flag CT feature
* 11.7 SOW 5 Merge Com and EQuery
* 11.8 SOW 6 Flexible Shipments List
11.9 SOW 9 Add TMS E0 attribute
11.10 SOW 10 Tune Role Admin
* 11.11 SOW 11 New Planner Profile
* 11.12 SOW 12 Shipments List for a Planner user
* 11.13 SOW 13 Approval related logic
* 11.14 SOW 14 Add FTL vs LTL flag and add Truck table for FTL
* 11.15 SOW 15 ASN transmit
11.16 SOW 16 ANA report
11.17 SOW 17 Jaguar Misc functionality
* 11.18 SOW 18 List of Portals and Portal Profile
* 11.19 SOW 19 New Shipper Profile
* 11.20 SOW 20 New ASN Form
* 11.21 SOW 21 Shipments List for a Shipper user
Retrieved from "https://wiki.jaguarfreight.com/ASN_20_BR"
Personal tools