ASN 20 BR

From UG

Revision as of 16:38, 11 September 2012 (edit) Alex (Talk | contribs) (→Misc) ← Older edit		Revision as of 16:40, 11 September 2012 (edit) (undo) Alex (Talk | contribs) (→Misc) Newer edit →
Line 75:		Line 75:
	== Misc ==		== Misc ==
		+
		+	=== Add Create GRP action to Virtual Group  ===
		+
		+	After ASN 20 is deployed more shipment will require grouping. Need additional mechanism to facilitate that.
	=== Add Clone User feature ===		=== Add Clone User feature ===

---

Revision as of 16:40, 11 September 2012

Contents 1 ASN 20 Core Needs 2 General BRBA 2.1 ASN Portal 2.2 Client specific MOTs 2.3 PO Issued By logic 3 Shipper and ASN form 3.1 Choice of mode for Shipper 3.2 Commodity line splits 3.3 For FCL offer Shipper to enter Container info 3.4 Dims and CBM management 4 Planner and Approval process 4.1 Approval mode is not same for all ASNs 4.2 Air Approval 5 Misc 5.1 Add Create GRP action to Virtual Group 5.2 Add Clone User feature 5.3 Simultaneous access to record by Shippers Planners and 3PL users/system for update 5.4 Add FTL vs LTL flag 5.5 Add Truck info 5.6 ASN transmit 5.7 Preliminary demo to EA

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 BRBA

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 system will create CT with rejected status notifying Shipper that he needs to re-submit.

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

Add Create GRP action to Virtual Group

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

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

• 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 #Add Truck info.

Add Truck info

For FTL shipments need truck related info such as:

• truck size
• 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.

Typical truck size values: 48 ft, 53 ft.

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)

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.