ASN 1.X

From UG

Revision as of 14:41, 24 November 2010 (edit) Denise (Talk | contribs) (→TDS Action Panel) ← Older edit		Current revision as of 14:27, 6 December 2012 (edit) (undo) Montira (Talk | contribs) (→SKU to Planner Mapping Feature)
(82 intermediate revisions not shown)
Line 8:		Line 8:
	Also see related glossary defined here: [[Cybertrax 2.1 Client (glossary)]]		Also see related glossary defined here: [[Cybertrax 2.1 Client (glossary)]]
		+
		+	This module is aka '''ASN 1.X'''
	== Functionality Overview ==		== Functionality Overview ==
Line 220:		Line 222:
	** Piece Price		** Piece Price
	** Total Value		** Total Value
		+
		+
	* Default order: Latest CT on top		* Default order: Latest CT on top
Line 260:		Line 264:
	* NOTE#1: Make E0.Client Company and MOT fields for all the shipments that were created by shippers to be READ ONLY fields on the internal application. Not allow operator to change E0.client company and MOT from the individual CT, group CT, etc.		* NOTE#1: Make E0.Client Company and MOT fields for all the shipments that were created by shippers to be READ ONLY fields on the internal application. Not allow operator to change E0.client company and MOT from the individual CT, group CT, etc.
	* NOTE#2: For the group case that contained some shipments that created by shipper, should have some validation and show err message that E0. client company/MOT cannot be changed if operator tries to change the E0.client company and/or to MOT to different company or MOT that was set as shipper user profile.		* NOTE#2: For the group case that contained some shipments that created by shipper, should have some validation and show err message that E0. client company/MOT cannot be changed if operator tries to change the E0.client company and/or to MOT to different company or MOT that was set as shipper user profile.
		+	* Prevent user to clone CT with unapproved and archived addresses.
	== Core Planner Functionality ==		== Core Planner Functionality ==
Line 269:		Line 274:
	* It is set in the Planner Profile section what is a part of Client Profile:		* It is set in the Planner Profile section what is a part of Client Profile:
	: 1) located in "Edit Non-Jaguar User" window what opens on the "Non-Jaguar Users" tab of "Admin - Users and Offices" section.		: 1) located in "Edit Non-Jaguar User" window what opens on the "Non-Jaguar Users" tab of "Admin - Users and Offices" section.
-	: 2) link to UI mock-up see [http://mantis.jaguarfreight.com/wiki/Cybertrax_2.1_Client_(use_cases)#Figure_1 here].	+	: 2) link to UI mock-up see [http://ct.jaguarfreight.com/wiki/Cybertrax_2.1_Client_(use_cases)#Figure_1 here].
	Planner's role for current non-jaguar user appoints through title checkbox of the Planner Profile section:		Planner's role for current non-jaguar user appoints through title checkbox of the Planner Profile section:
Line 419:		Line 424:
	[b] Status can be changed to Approved, Rejected or Hold Without Approved For Pick Up On Date Status		[b] Status can be changed to Approved, Rejected or Hold Without Approved For Pick Up On Date Status
		+	* Reject status cannot be applied to a CT record that has an "Approved for pick up on" date set within 72 hrs.  See [[#Approve for pick up on date constraint]] for ref
	[c] This date maybe changed to another date or cleared as many times as required but is subject to [[#Approve for pick up on date constraint]] constraint - see below.		[c] This date maybe changed to another date or cleared as many times as required but is subject to [[#Approve for pick up on date constraint]] constraint - see below.
Line 460:		Line 466:
	All authorization events must be posted. Something like		All authorization events must be posted. Something like
-	[[File:HistoryWindow.JPG]].	+	[[File:HistoryWindow.JPG|800px]].
	=== Notification feature ===		=== Notification feature ===
Line 721:		Line 727:
	* Note: For the phone number as Pick up location and delivery location example below, it will show when there is any phone number on the address book.		* Note: For the phone number as Pick up location and delivery location example below, it will show when there is any phone number on the address book.
-	See example below:	+	* Change request - add different terms according to the Pick up & Delivery location
		+	** If Pickup location [[CT_bo#Export_Pick_Up]] = Elizabeth Arden 1751 Blue Hills Drive Roanoke, VA 24012 make freight terms are Pre-Paid
		+	** If Delivery location [[CT_bo#Export_Delivery_To]] = Elizabeth Arden 1751 Blue Hills Drive Roanoke, VA 24012 make freight terms are Pre-Paid
		+	** All else, leave as Third Party billing to Elizabeth Arden 1751 Blue Hills Drive Roanoke, VA 24012
		+
		+	See Collect example attached to Mantis [[http://ct.jaguarfreight.com/mantis/view.php?id=3140 3140]]
		+
		+	See Pre-Paid example attached to Mantis [[http://ct.jaguarfreight.com/mantis/view.php?id=3140 3140]]
		+
		+	See Third Party example below:
	<pre>		<pre>
Line 732:		Line 747:
	Dear Mary <this is the shipper who created the CT records>,		Dear Mary <this is the shipper who created the CT records>,
-	The following shipment has been <bold>APPROVED</bold> and will be picked up by: Jewels Transportation <this should be the truckers name only and in bold>.	+	The following shipment has been APPROVED and will be picked up by: Jewels Transportation <this should be the truckers name only and
-	<bold>Please ensure that our reference - CT # 11111, <this is the record #> is clearly recorded on your truck bill of lading</bold>.	+	in bold>. Please ensure that our reference - CT # 11111, <this is the record #> & Load # <this is the load # received from TMS> are
		+	clearly recorded on your truck bill of lading.
	Pickup Location:-><bold>                Delivery Location:-><bold>		Pickup Location:-><bold>                Delivery Location:-><bold>
Line 749:		Line 765:
	<This should be the same information that’s listed on the contents table wording & all>		<This should be the same information that’s listed on the contents table wording & all>
		+
		+	Freight Charges: <bold and underline>
		+	Third Party Billing to Elizabeth Arden - 1751 Blue Hills Drive - Roanoke, VA 24012 <bold>
		+
	To view this online in CyberTrax 2.0, please follow this link: CT# 11111 <CT#hyperlink>		To view this online in CyberTrax 2.0, please follow this link: CT# 11111 <CT#hyperlink>
Line 769:		Line 789:
	Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available		Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available
	upon request.		upon request.
		+	</pre>
		+
		+	=== System Auto-Reject Email Notification ===
		+	<pre>
		+	From: cybertrax@jaguarfreigh.com <System e-mail address>
		+	Sent: Friday, Jan 14, 2011 12.01 AM <Date time sent>
		+	To: mary@jackel.com <this is the shipper who created the CT records>
		+	Subject: Rejection Notification for CT 11113
		+
		+
		+	Dear Mary <this is the shipper who created the CT records>,
		+
		+	The following shipment has been REJECTED as per the details below.
		+
		+	Status       Comment                                       Last Update                      Updated By
		+	REJECTED  This shipment has been automatically                14-Jan-2011 12:01 AM EST          System
		+	rejected by the system, due to 90 days
		+	of inactivity.
		+	Please contact the appropriate purchasing
		+	group for any further information
		+
		+
		+	Pickup Location: Delivery Location:
		+	CEI Holmdel                              Gannet Warehouse
		+	2182 Rte 35 S                            50 Executive Ave
		+	Holmdel, NJ 07733                    Edison, NJ 08817
		+	Phone: xxx.xxx.xxx                      Phone: xxx.xxx.xxx
		+
		+	CT 11113
		+	PO    SKU  Qty  Item Description  # Plts    Pkgs on Plts  Loose Pkgs  TTL GW (lb)  Haz  Stack
		+	---      ---      --      -------                        ----      ----                  ---                ---                ---    --
		+
		+	To view this online in CyberTrax 2.0, please follow this link: CT# 11113 <CT# hyperlink>
		+
		+	Please do not reply to this message as it is not an actively monitored e-mail address.
		+
		+	Kind Regards,
		+	EA USA Domestic Team
		+	at
		+	Jaguar Freight Services
		+	10 Fifth Street 3rd floor
		+	Valley Stream, NY 11581
		+	Tel: +1 516-239-1900
		+	Fax: +1 516-239-6300
		+	www.jaguarfreight.com
		+
		+	Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
		+
		+	Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available upon request.
	</pre>		</pre>
Line 821:		Line 890:
	=== Search feature on List CTs ===		=== Search feature on List CTs ===
-	* Filter to search each column on each tab, excluding dates and money	+	* Filter to search each column on each tab
		+	:* Number of records on all tabs
		+	:* Download to Excel Button
		+	:* See Detail for [[Web_Portal_Search_Line_Download_to_Excel]]
		+
		+	=== History Log ===
		+	* It is a log history for a field to view any action that has been done for a particular field. These history will record date time that record has been updated, value of the field, and the field has been updated by.
		+	* Similar feature to [[History_of_Date]]
		+	* Apply to these fields:
		+	:* Pickup Trucker Name
		+	:* Estimated PickUp Date
		+	:* Actual PickUp Date
		+	:* Delivery Trucker
		+	:* Estimated Delivery Date
		+	:* Actual Delivery Date
		+	:* All of the above updates that are made via the TMS, should display on the history log
		+
		+	[[File:HistoryWebportal.JPG|800px]]
	=== Constraint for Archived Tab for Shipper and Planner ===		=== Constraint for Archived Tab for Shipper and Planner ===
Line 897:		Line 983:
	Please note that all business is transacted subject to our general business terms and conditions, as indicated on our freight invoices and HB/L, a copy of which is also available upon request.		Please note that all business is transacted subject to our general business terms and conditions, as indicated on our freight invoices and HB/L, a copy of which is also available upon request.
	</pre>		</pre>
		+
		+	=== Support Link ===
		+	Allow clients who has question(s) about the web portal to email to the right support group of people
		+	* URL link to eadom@jaguarfreight.com
		+	* URL labe: Portal Shipment Support
		+	* Apply for both Shipper and Planner Interface
		+	* See [[File:PortalSupport.JPG|800px]]
		+	=== Web Portal Search Line Download to Excel===
		+	See [http://ct.jaguarfreight.com/wiki/Web_Portal_Search_Line_Download_to_Excel Download to Excel]
		+
		+
		+	=== SKU column width and Copy feature ===
		+	* Field: SKU
		+	:* Width of SKU column to show 16 characters
		+	:* Provide copy text functionality from shipment list table on Web Portal
		+	:** The width of SKU column will be increased to handle 16 characters, so that user can read the full SKU number without clicking into each CT record. Ability of right click submenu for copy data field can be provided for SKU and PO, so that “Copy” functionality will allow user to copy the text of SKU or PO field and paste it anywhere they want for their convenient.
		+	:* See Figure below:
		+	[[File:SKU1.JPG|800px]]
		+
		+
		+	=== When 2 planners set ANY Status to the same record at the same time ===
		+
		+	*Case found: 2 different planners at the same time, set 2 different status to the same CT record. The system replaces the last value set, but does not warn user that someone else set a status to the record as well.
		+
		+	*Solution: Add warning message to advise user to refresh their browser as another user has already set a status.
		+
		+	==== Warning Refresh Message ====
		+
		+	[[File:User receives message 302424 at same time.JPG|800px]]
		+
		+
		+	=== Automatic Shipment Rejection Function ===
		+
		+	* System will automatically rejects all the shipments on New Tab that have Created On Date value greater than 90 days compared to today date.
		+	* Rejected shipments will be moved to the Rejected Tab.
		+	* E-mail notification will be sent out to notify the shipper who created the CT record that “This shipment has been automatically rejected by the system, due to 90 days of inactivity. Please contact the appropriate purchasing group for any further information.” See [[#System_Auto-Reject_Email_Notification]]
		+	* This status will be recorded on the history log
	== Truck Domestic Stats TDS feature ==		== Truck Domestic Stats TDS feature ==
Line 929:		Line 1,052:
	**routed, but not picked up		**routed, but not picked up
	**picked, up but not delivered		**picked, up but not delivered
-	* Should list the [[CT_bo#TMSS_field]] for each record - See [[#Figure_]]	+	* Should list the [[CT_bo#TMSS_field]] for each record - See [[#TMSS_on_TDS]]
	* CT's must satisfy these conditions for each status category:		* CT's must satisfy these conditions for each status category:
Line 975:		Line 1,098:
	**HU		**HU
	**Gross Weight (LB)		**Gross Weight (LB)
		+	**TMS Status
	* '''Columns for Routed Tab:'''		* '''Columns for Routed Tab:'''
Line 990:		Line 1,114:
	**Pick up Trucker		**Pick up Trucker
	**Estimated Pick up Date		**Estimated Pick up Date
		+	**TMS Status
	* '''Columns for Picked Up Tab:'''		* '''Columns for Picked Up Tab:'''
Line 1,008:		Line 1,133:
	**Delivery Trucker		**Delivery Trucker
	**Estimated Delivery Date		**Estimated Delivery Date
		+	**TMS Status
	* Default order: Latest CT on top		* Default order: Latest CT on top
Line 1,041:		Line 1,167:
	** [[CT_bo#PT Number]]		** [[CT_bo#PT Number]]
	** Now including upload to TMS option		** Now including upload to TMS option
-	*** See [[Update_Fields_for_Virtual_Group#Updated_business_requirements_11.2F2010_as_TM_is_now_used]]	+	*** See [[Update_Fields_for_Virtual_Group#Updated_business_requirements_11.2F2010_as_TM_is_now_used]]  AND  [[#TMS_Upload_on_Virtual_Group]]
	* '''1 New Virtual Group Interface field:'''		* '''1 New Virtual Group Interface field:'''
	** [[CT_#Consol_Warehouse]]		** [[CT_#Consol_Warehouse]]
-	== New Pending Address (NPA) Feature ==	+	===== TMSS on TDS =====
		+
		+	[[File:VG TM Upload 4.JPG|800px]]
		+
		+	===== TMS Upload on Virtual Group =====
		+
		+	[[File:VG TM Upload.JPG|800px]]
		+
		+	== New Pending Address (NPA) Feature (Disable for now) ==
	==== Core Need ====		==== Core Need ====
Line 1,200:		Line 1,334:
	See new example on figure below:		See new example on figure below:
-	[[File:New Sku to Planner Map.JPG]]	+	[[File:New Sku to Planner Map.JPG|800px]]
	=== Planner filter ===		=== Planner filter ===
Line 1,233:		Line 1,367:
	=== Upload panel for SKU to Planner map ===		=== Upload panel for SKU to Planner map ===
	==== Figure 1. SKU to Planner map ====		==== Figure 1. SKU to Planner map ====
-	[[File:UploadSKUtoPlanner.JPG]]	+	[[File:UploadSKUtoPlanner.JPG|800px]]
	==== Figure 2. Warning Message for upload a file ====		==== Figure 2. Warning Message for upload a file ====
-	[[File:UploadWarning.JPG]]	+	[[File:UploadWarning.JPG|800px]]
	==== Figure 3. Incorrect format of uploaded file ====		==== Figure 3. Incorrect format of uploaded file ====
-	[[File:IncorrectUploadedFile.JPG]]	+	[[File:IncorrectUploadedFile.JPG|800px]]
	=== Shipment list with Planner filter ===		=== Shipment list with Planner filter ===
Line 1,247:		Line 1,381:
	==== Figure 4. Planner Portal for BASIC PLANNER with Planner's name filter ====		==== Figure 4. Planner Portal for BASIC PLANNER with Planner's name filter ====
-	[[File:MOCKUp2.JPG]]	+	[[File:MOCKUp2.JPG|800px]]
	==== Figure 5. Planner Portal for SUPER PLANNER with Planner's name filter  ====		==== Figure 5. Planner Portal for SUPER PLANNER with Planner's name filter  ====
-	[[File:MOCKUp3.JPG]]	+	[[File:MOCKUp3.JPG|800px]]
		+
		+	=== SKU TO PLANNER UPDATED ===
		+	* Change to upload CSV file only
		+	* Line and Columns are the same
		+	* Note - there are some SKU that contains E+ symbols - it's incorrect.. BEFORE exporting to csv format, we should CONVERT SKU column to TEXT format INSTEAD of numeric.. It will prevent representing sku values in scientific format, like "xxxE+xxx"
	== Double Approval Process Feature ==		== Double Approval Process Feature ==
Line 1,277:		Line 1,416:
	'''NEW TAB'''		'''NEW TAB'''
-	* New shipments and shipments that were approved by basic planners are located on New Tab	+	* New shipments, shipments that were approved by basic planners and placed on hold by basic planners are located on the New Tab
-	** Differentiate these two types of shipments with color flags:	+	** Differentiate these three types of shipments with color flags:
-	*** New shipments with '''white''' flags - these shipments are new and waiting for an approval	+	*** New shipments with '''white''' flags - these shipments are new and waiting for an approval.
	*** Approved shipments with '''orange''' flags - these shipments were approved by basic planners and are waiting for the final approval from the super planner.		*** Approved shipments with '''orange''' flags - these shipments were approved by basic planners and are waiting for the final approval from the super planner.
		+	*** Hold with or without a date shipments with '''yellow''' flags - these shipments were placed on hold by basic planners and are waiting for the final approval from the super planner.
-	* Shipments that were placed on hold with a date and the system automatically approves, will be located on the New Tab	+	* Shipments that were placed on hold with a date and the system automatically approves, will remain on the New Tab.
-	* Planner's name column is needed for super planner ONLY	+	* Planner's name column is needed for super planner ONLY.
-	* Piece Price column is needed ONLY for basic planners but NOT super planners	+	* Piece Price column is needed ONLY for basic planners but NOT super planners.
	'''APPROVED TAB'''		'''APPROVED TAB'''
-	* Shipments that were approved by super planner(s) are located on the Approved Tab with '''Green''' flags	+	* Shipments that were approved by super planner(s) are located on the Approved Tab with '''Green''' flags.
	'''HOLD TAB'''		'''HOLD TAB'''
-	* Shipments that are placed on hold by a basic planner and a super planner appear here	+	* Shipments that are placed on hold by a super planner appear here and have a yellow flag.
-	* Basic planner can set an approval status to all shipments that are placed on hold even by a super planner	+	* Basic planner cannot set an approval status to shipments that are placed on hold by a super planner.
	'''REJECTED TAB'''		'''REJECTED TAB'''
-	* Shipments that are rejected by basic and super planners	+	* Shipments that are rejected by basic and super planners.
	'''DELIVERED TAB'''		'''DELIVERED TAB'''
-	* No changes from original functionality	+	* No changes from original functionality.
	'''ARCHIVED TAB'''		'''ARCHIVED TAB'''
-	* No changes from original functionality	+	* No changes from original functionality.
-	'''3) Approval status panel'''  [[File:SetApprovalPanel.JPG]]	+	'''3) Approval status panel'''  [[File:SetApprovalPanel.JPG|800px]]
	'''It will appear on the "NEW TAB"'''		'''It will appear on the "NEW TAB"'''
	* Basic planner: Y only for white flagged shipments		* Basic planner: Y only for white flagged shipments
-	* Super planner: Y for all shipments (white and orange flagged shipments)	+	* Basic planner: Y only for orange flagged shipments
		+	* Basic planner: Y with for yellow flagged shipments "Approved for Pick Up On:" yellow flag
		+	* Super planner: Y for all shipments (white, orange & yellow flagged shipments)
	'''To appear on the "APPROVED", "DELIVERED", and "ARCHIVED" TABS'''		'''To appear on the "APPROVED", "DELIVERED", and "ARCHIVED" TABS'''
Line 1,321:		Line 1,463:
	'''To appear on the "HOLD TAB"'''		'''To appear on the "HOLD TAB"'''
-	* Basic planner: Y with "Approved for Pick Up On:" date panel
	* Super planner: Y with "Approved for Pick Up On:" date panel		* Super planner: Y with "Approved for Pick Up On:" date panel
Line 1,374:		Line 1,515:
	[b] Basic planner(s) are able to set an approval status (Approve, Reject, Hold, and Hold with Date) as normal functionality		[b] Basic planner(s) are able to set an approval status (Approve, Reject, Hold, and Hold with Date) as normal functionality
-	[c] Basic planner(s) cannot set an approval status to the shipments on New Tab that are already approved, or have an '''orange''' flag	+	[c] Basic planner(s) can change/set an approval status to the shipments on New Tab that are already approved, or have an '''orange''' flag to (New, Approve, Reject, Hold, and Hold with Date) and have Cargo Due date set to a future date that is at least over 72 hrs from current date.
-	[d] Approval status panel is disabled for shipments that have an '''orange''' flag. The panel will be replaced by "This shipment is pending final approval by a super planner"	+	[d] Basic planner(s) can change/set an approval status to the shipments on New Tab that are already on hold with a date, or have an '''yellow''' flag to (New, Approve, Reject, Hold, and Hold with Date).
		+
		+	[e] Basic planner(s) can change/set an approval status to the shipments on New Tab that are already on hold, or have an '''yellow''' flag to (New, Approve, Reject, Hold, and Hold with Date).
	==== Super Planners ====		==== Super Planners ====
	[a] Each planner is able to see and set approval status, to any shipments by using [[#Planner filter]]. See [[#SKU to Planner Mapping Feature]]		[a] Each planner is able to see and set approval status, to any shipments by using [[#Planner filter]]. See [[#SKU to Planner Mapping Feature]]
-	[b] Super planner(s) are also able to approve the shipments that have an '''orange''' or '''white''' flag (all shipment on New Tab)	+	[b] Super planner(s) are also able to approve the shipments that have an '''orange''' or '''white''' or '''yellow''' flag (all shipments are found on the New Tab)
	[c] Super planner(s) are able to set an approval status to (Approve, Reject, Hold, and Hold with date) as normal functionality		[c] Super planner(s) are able to set an approval status to (Approve, Reject, Hold, and Hold with date) as normal functionality
Line 1,393:		Line 1,536:
	=== Planner's role configuration ===		=== Planner's role configuration ===
	==== Figure 1. Example of basic planner configuration user profile ====		==== Figure 1. Example of basic planner configuration user profile ====
-	[[File:BasicPlanner.JPG]]	+	[[File:BasicPlanner.JPG|800px]]
	==== Figure 2. Example of super planner configuration user profile ====		==== Figure 2. Example of super planner configuration user profile ====
-	[[File:SuperPlanner.JPG]]	+	[[File:SuperPlanner.JPG|800px]]
		+
		+	== SOW 1 ==
		+
		+	Mantis [http://ct.jaguarfreight.com/mantis/view.php?id=3382 3382]
		+
		+	Core Requirements:
		+	* Change the auto reject # of days property from hard coded (90 days) to an editable field that Admin Users may edit and maintain.
		+	** Name "editable field" - Automatically reject shipments on New tab after NNN days of inactivity"
		+
		+	See [[#Automatic Shipment Rejection Function]]
	== History ==		== History ==
	=== 0002467: [EDI to TMS] (Misc) TDS functionality for TMS ===		=== 0002467: [EDI to TMS] (Misc) TDS functionality for TMS ===
		+
		+	=== 0002290: [Client 2.2] Shipper/Planner functionality (phase 2) - TDS Changes ===
		+	* Virtual Group changes
		+
		+	=== 0002559: TDS date fetching refactoring ===
		+	*Bug/Chng to TDS, Kostya had to implement dates distibution thru Calendar class, not Date
		+
		+	=== 0002480: [EDI to TMS] chg: add TMSS column to other tabs: Routed, Picked Up  ===
		+
		+	=== 0002567: [EDI to TMS] Shipment(s) that is updated by TM does not save the updated date on date field and on history on Web portal ===
		+
		+	=== 0002531: Add link for web portal support inside the portal for client to email to the right group of people  ===
		+	* [http://mantis.jaguarfreight.com/mantis/view.php?id=2531 2531]
		+	* See [http://mantis.jaguarfreight.com/wiki/Cybertrax_2.1_Client_%28requirements%29#Support_Link Support Link]
		+	* Spec is updated: Yes
		+
		+	=== 0002485: [ClientSP ph3] Option to download portal records on all tabs into an xls format with some sort of filters ===
		+	* [http://mantis.jaguarfreight.com/mantis/view.php?id=2485 2485] See attached file on the mantis
		+	* Spec is updated: Yes
		+
		+	=== 0002622: [EDI to TMS ph2] Disable Approved CT Record sent to TMS message for planner role on client app ===
		+
		+	=== 0002986: [EDI to TMS] Change: Add Load# to E-mail dispatch notification sent to shipper user for planner approved CT when load plan rcvd  ===
		+	* Spec is updated: Yes
		+
		+	=== 0002638: Increase width SKU column to show 16 characters and provide copy text functionality from shipment list table on Web Portal ===
		+	* Spec is updated: Yes
		+
		+	=== 0002642: Allow basic planner to "unapprove" an item or be able to reject something that they had approved. ===
		+	*Spec is updated: Yes
		+
		+	=== 0002643: Hold status by Basic planner should stay on New Tab with a color coded ===
		+	*Spec is updated: Yes
		+
		+	=== 0002669: Automated shipment rejection for new shipments that has been created more than 30 days<proj> ===
		+	*Spec is updated: Yes
		+
		+	=== 0003208: [EA - Enhancement (Truck-Dom)] Change: Don't allow Rejct Status for Hold w/ Approved for CTs that are w/in 72 hrs of set date ===
		+	*Spec is updated: Yes
		+
		+	=== 0003372: Change: Automated Shipment Rejection Feature - change hard coded # of days from 30 to 90 ===
		+	'''This change will be implemented in Jan 2012 release'''
		+	*Spec is updated: Yes

---

Current revision as of 14:27, 6 December 2012

Right version

Contents 1 Introduction 2 Functionality Overview 2.1 Summary 3 Core Shipper Functionality 3.1 Creating Shipper User and Shipper Profile 3.2 Create CT record 3.2.1 CT preview and disclaimer screen 3.2.2 CT confirmation screen 3.2.3 Constraint on the number of lines in Commodity table in CTs created by Shipper User 3.2.4 Show only US and Canadian addresses 3.2.5 Mark validation clearly 3.3 View list of CT records as a shipper 3.4 Edit CT record 3.4.1 What CTs Shipper may edit RULE 3.4.2 When to lock CT record for edit by Shipper RULE 3.5 Delete CT records 3.5.1 What CTs Shipper may delete RULE 3.5.2 When to lock CT record for delete by Shipper RULE 3.5.3 Field for text box/area that must be read only on Add/Clone shipments 3.6 Clone CT Record 3.6.1 Clone feature Exception 4 Core Planner Functionality 4.1 Creating Planner User and Planner Profile 4.2 View list of CT records as a planner 4.3 Authorize CT records 4.3.1 Approve Status 4.3.2 Reject Status 4.3.3 Hold Without Approved For Pick Up On Date Status 4.3.4 Hold With Approved For Pick Up On Date Status 4.3.4.1 Approve for pick up on date constraint 5 Core Jaguar Functionality 5.1 CT profile on Internal for CTs created by Shipper 5.2 See also 6 Misc Functionality 6.1 Planner comments screen 6.1.1 Authorization History 6.2 Notification feature 6.2.1 Receipt for created CT by Shipper 6.2.2 Planner Notification Emails 6.2.2.1 Status notification Approved 6.2.2.2 Status notification Reject without a comment 6.2.2.3 Status notification Reject with a comment 6.2.2.4 Status notification Hold without a date 6.2.2.5 Status notification Hold with a date 6.2.3 Notification when trucker assigned by Jaguar 6.3 System Auto-Reject Email Notification 6.4 One user with multiple roles feature 6.5 See Also 6.6 Creating CT records by cloning feature 6.7 Admin for PO issued by CT field 6.8 Admin for Trailer Per Load 6.9 Search feature on List CTs 6.10 History Log 6.11 Constraint for Archived Tab for Shipper and Planner 6.12 Shipment accessibility 6.13 Email confirmation for shipper account created 6.14 Email confirmation for planner account created 6.15 Support Link 6.16 Web Portal Search Line Download to Excel 6.17 SKU column width and Copy feature 6.18 When 2 planners set ANY Status to the same record at the same time 6.18.1 Warning Refresh Message 6.19 Automatic Shipment Rejection Function 7 Truck Domestic Stats TDS feature 7.1 Core need 7.2 TDS Solution Overview 7.3 Dashboard 7.3.1 Refresh frequency for Dashboard 7.3.2 TDS option in Jag User profile 7.4 TDS Dashboard Panel 7.4.1 Approved status 7.4.2 Routed status 7.4.3 Picked Up status 7.5 TDS Action Panel 7.5.1 TMSS on TDS 7.5.2 TMS Upload on Virtual Group 8 New Pending Address (NPA) Feature (Disable for now) 8.1 Core Need 8.2 NPA Dashboard 8.3 Shipper NPA Process 8.3.1 Create New Address fields 8.4 Jag Internal NPA Process 9 SKU to Planner Mapping Feature 9.1 Core requirement 9.2 Functionality Overview 9.3 Group of planers to see Planer filter 9.4 SKU to Planner map 9.5 Planner filter 9.6 Upload panel for SKU to Planner map 9.6.1 Figure 1. SKU to Planner map 9.6.2 Figure 2. Warning Message for upload a file 9.6.3 Figure 3. Incorrect format of uploaded file 9.7 Shipment list with Planner filter 9.7.1 Figure 4. Planner Portal for BASIC PLANNER with Planner's name filter 9.7.2 Figure 5. Planner Portal for SUPER PLANNER with Planner's name filter 9.8 SKU TO PLANNER UPDATED 10 Double Approval Process Feature 10.1 Core requirement 10.2 Functionality Overview 10.2.1 Summary 10.2.2 Basic Information for this feature 10.2.3 Profile Setting 10.2.4 Basic Planners 10.2.5 Super Planners 10.3 Misc Functionality 10.4 Planner's role configuration 10.4.1 Figure 1. Example of basic planner configuration user profile 10.4.2 Figure 2. Example of super planner configuration user profile 11 SOW 1 12 History 12.1 0002467: [EDI to TMS] (Misc) TDS functionality for TMS 12.2 0002290: [Client 2.2] Shipper/Planner functionality (phase 2) - TDS Changes 12.3 0002559: TDS date fetching refactoring 12.4 0002480: [EDI to TMS] chg: add TMSS column to other tabs: Routed, Picked Up 12.5 0002567: [EDI to TMS] Shipment(s) that is updated by TM does not save the updated date on date field and on history on Web portal 12.6 0002531: Add link for web portal support inside the portal for client to email to the right group of people 12.7 0002485: [ClientSP ph3] Option to download portal records on all tabs into an xls format with some sort of filters 12.8 0002622: [EDI to TMS ph2] Disable Approved CT Record sent to TMS message for planner role on client app 12.9 0002986: [EDI to TMS] Change: Add Load# to E-mail dispatch notification sent to shipper user for planner approved CT when load plan rcvd 12.10 0002638: Increase width SKU column to show 16 characters and provide copy text functionality from shipment list table on Web Portal 12.11 0002642: Allow basic planner to "unapprove" an item or be able to reject something that they had approved. 12.12 0002643: Hold status by Basic planner should stay on New Tab with a color coded 12.13 0002669: Automated shipment rejection for new shipments that has been created more than 30 days<proj> 12.14 0003208: [EA - Enhancement (Truck-Dom)] Change: Don't allow Rejct Status for Hold w/ Approved for CTs that are w/in 72 hrs of set date 12.15 0003372: Change: Automated Shipment Rejection Feature - change hard coded # of days from 30 to 90

[edit] Introduction

To streamline a business process of submitting and approving shipments at Elizabeth Arden it is proposed to provide a web portal. Required software is a tool that allows a supplier to enter an Elizabeth Arden domestic traffic order. It also allows for a planner or E.M. to approve, reject or hold any order that has been entered. The main goal of this is to put the right people in contact with the supplier.

There are a number of features that should be postponed and released in phase two. This was done to launch portal with core features as soon as possible.

Also see related glossary defined here: Cybertrax 2.1 Client (glossary)

This module is aka ASN 1.X

[edit] Functionality Overview

[edit] Summary

Existing Cybertrax Client web portal should support two additional user roles:

• Shipper (a.k.a. Supplier)
• Planner (a.k.a. EM)

Internal (Jaguar)user will also have some additional functionality.

Core Shipper User Functionality:

• create CT record
• edit CT record
• delete CT record
• view CT records
• notifications
• appropriate visibility

Core Planner User Functionality:

• view CT record
• set "approval status" on selected CT record
• notifications
• appropriate visibility

Client Functionality and Changes:

• should not be affected

Core Jaguar User and Cybertrax Internal Functionality:

• non jaguar user profile will have 3 roles defined
• Jaguar User will see new additional fields
• Jaguar User will see only shipments on Live tab when the CT has been approved by a planner, place on hold with date 72 hours before it is approved by system.
• constraint on how many lines commodity table might have
• some fields might become read only
• additional report
• new address approval process
• etc

[edit] Core Shipper Functionality

[edit] Creating Shipper User and Shipper Profile

All CTs created by specific Shipper user must have same:

• MOT
• E0
• Shipper

NOTE: These parameters must be defined in the Shipper Profile which is a part of the Client Profile:

1) located in "Edit Non-Jaguar User" window what opens on the "Non-Jaguar Users" tab of "Admin - Users and Offices" section.

2) link to UI mock-up see here.

Shipper's role for current non-jaguar user appoints through title checkbox of the separate Shipper Profile section:

• label - "Enable Shipper/Supplier role".
• functionality - when checkbox is checked then user is a Shipper.

There are two additional labels below the checkbox.

• First label contains the text: "The role allow user to add CTs".
• Second label contains the text: "Create CT with" and means an ability for user as a Shipper to create CTs with Shipper's parameters - MOT, E0, Shipper.

Parameters of Shipper's role what was listed above are filled and stored in the three dropdown lists:

• MOT:

label - "MOT:"

definition:

value - now is used only one MOT = Trucking-Domestic (in the future will be selected from dropdown list with set of MOT).

• E0

label - "E0. Client Companies:"

definition:

value - must be selected one from the list of Client companies. This list reflects the set of records from "Admin > Client Companies".

• Shipper

label - "Shipper (T1):"

definition:

value - must be selected one from the list of Shippers. This list reflects the set of records from "Admin > Address Book > Transportation" with T1="Yes".

[edit] Create CT record

• [a] Shipper will be able to add Cybertrax 2.1 Client (glossary)#Shipping request once the product is ready to ship.

• [b] See detailed definitions of shipments fields in Cybertrax 2.1 Client (data dictionary).

• [c] They can enter a number of lines of PO/SKU’s for only one E.M. at a time, including the piece price per PO/SKU.

• [d] System will create one CT record per commodity line.

• [e] Upon saving the information entered, an automatic validation notification will “pop up” asking the user to review the following information that they entered, noting the disclaimer. Read more here: CT preview and disclaimer screen

• [f] Upon user clicking save:
  • automatic confirmation will pop up, reconfirming the information entered, including the shipment CT records. Read more here: CT confirmation screen
  • email will be generated, see #Receipt for created CT by Shipper

• [g] Records created by a shipper company should display for ALL users who are a part of the same shipper company

[edit] CT preview and disclaimer screen

This screen is for the operator to "review" and "confirm" that the information they entered is correct.

This screen should contain the following information:

• PO issued by value
• Ship from value
• Ship to value
• PO value per commodity line
• SKU value per commodity line
• Quantity value commodity per line
• Cargo Available Date
• Disclaimer:
  • Failure to have the shipment available for pick up on the available date will result in chargeback’s.

[edit] CT confirmation screen

This is a confirmation to the supplier of the information they just entered and should contain the following information:

• Number of CT records created
• PO issued by value
• Ship from value
• Ship to value
• List of the CT record numbers
• Users Name
• Date and time stamp
• Should allow user to print for their records

[edit] Constraint on the number of lines in Commodity table in CTs created by Shipper User

Commodity table in CTs created by Shipper may have only ONE line.

[edit] Show only US and Canadian addresses

Show only US and Canadian addresses in:

• Ship to Location
• Pick up Location

[edit] Mark validation clearly

1) Add red star to required field 2) Add note to the screen "Both Loose Pkgs and Plts cant be zero at the same time on one line."

[edit] View list of CT records as a shipper

• Shipper can view records that anyone in their company created.
• Columns heading should have mouse over label (description).
• Shipper should have ability to print the CT record that they view (print friendly)
• View CTs table definitions:

• Columns for New Tab:
  • CT Record
  • Created On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Approved Tab:
  • CT Record
  • Approved On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Hold Tab:
  • CT Record
  • Approved For
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Rejected Tab:
  • CT Record
  • Rejected On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Delivered Tab:
  • CT Record
  • Created On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Archived Tab:
  • CT Record
  • Created On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Default order: Latest CT on top
• Sortable?: Yes, ascending and descending,throughout all the shipments for all pages
• Search feature: See #Search_feature_on_List_CTs
• Action buttons per tab definitions:
  • Action Buttons for New Tab: Add, Copy or Clone, View, Edit, Delete
  • Action Buttons for Approved Tab: Copy or Clone, View
  • Action Buttons for Hold Tab: Copy or Clone, View
  • Action Buttons for Rejected Tab: Copy or Clone, View
  • Action Buttons for Archived Tab: Copy or Clone, View
  • Action Buttons for Delivered Tab: Copy or Clone, View

[edit] Edit CT record

[edit] What CTs Shipper may edit RULE

• Shipper user may edit only records she created

[edit] When to lock CT record for edit by Shipper RULE

• Shipper may edit an existing CT before it is approved or placed on hold or rejected by a planner.

[edit] Delete CT records

[edit] What CTs Shipper may delete RULE

• Shipper user may delete only records she created

[edit] When to lock CT record for delete by Shipper RULE

• Shipper may delete an existing CT before it is approved by a planner, placed on hold by a planner or rejected by a planner.

[edit] Field for text box/area that must be read only on Add/Clone shipments

• Shipper
• Pick up Location
• Ship to Location
• Created By
• Total Value

[edit] Clone CT Record

[edit] Clone feature Exception

• Cargo Available Date: This should be the current date, do not copy the clone date
• E0.Client Company: This should be the same as it is set on Shipper user profile, do not copy the clone E0.Client Company
• MOT: This should be the same as it is set on Shipper user profile, do not copy the clone MOT
• NOTE#1: Make E0.Client Company and MOT fields for all the shipments that were created by shippers to be READ ONLY fields on the internal application. Not allow operator to change E0.client company and MOT from the individual CT, group CT, etc.
• NOTE#2: For the group case that contained some shipments that created by shipper, should have some validation and show err message that E0. client company/MOT cannot be changed if operator tries to change the E0.client company and/or to MOT to different company or MOT that was set as shipper user profile.
• Prevent user to clone CT with unapproved and archived addresses.

[edit] Core Planner Functionality

[edit] Creating Planner User and Planner Profile

Planner user has an attribute PO issued by that regulates what CTs planner may see/authorize.

• This attribute may have more than one value.
• It is set in the Planner Profile section what is a part of Client Profile:

1) located in "Edit Non-Jaguar User" window what opens on the "Non-Jaguar Users" tab of "Admin - Users and Offices" section.

2) link to UI mock-up see here.

Planner's role for current non-jaguar user appoints through title checkbox of the Planner Profile section:

• label - "Enable Authorization/Planner/EM role".
• functionality - when checkbox is checked then user is a Planner.

There is two additional labels below the checkbox.

• First label contains the text: "The role allow user to authorize CTs".
• Second label contains the text: "Authorize CTs with" and means an ability for user as a Planner to authorize CTs with appropriate "PO issued by" attribute.

"PO issued by" as attribute of Planner's role are selected from combobox and stored in the listbox:

• combobox label - "PO issued by"
• combobox value - must be selected from special list of companies. This list are managed from Admin and contains some of manually entered names of companies. For now the list includes next values: CEI Holmdel, EA Stamford, CEI Roanoke, Kolmar, Kik, Evergreen.
• list of "PO issued by" values stores in listbox. This list can be edited (add/delete line by line) and fully cleared.

[edit] View list of CT records as a planner

• [a] Planners may view only all records they have visibility to.
• [b] Visibility is defined through PO issued by CT field defined in Planners profile.
• [c] Planners should have ability to print the CT record that they view (print friendly)
• [d] View CTs table definitions:

• Columns for New Tab:
  • CT Record
  • Created On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Approved Tab:
  • CT Record
  • Approved On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Hold Tab:
  • CT Record
  • Approved For
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Rejected Tab:
  • CT Record
  • Rejected On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Delivered Tab:
  • CT Record
  • Created On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Columns for Archived Tab:
  • CT Record
  • Created On
  • Pick Up Location
  • Delivery Location
  • PO
  • SKU
  • Qty
  • Piece Price
  • Total Value

• Default order: Latest CT on top
• Sortable?: Yes, ascending and descending, throughout all the shipments for all pages
• [d] Search feature: See #Search_feature_on_List_CTs
• [e] Action buttons per tab definitions:
  • Action Buttons for New Tab: Set approve status (approve, hold, reject) & View
  • Action Buttons for Approved Tab: Set approve status (approve, hold, reject) & View
  • Action Buttons for Hold Tab: Set approve status (approve, hold, reject), View and Set Approved for Pick Up On:
  • Action Buttons for Rejected Tab: View
  • Action Buttons for Archived Tab: View
  • Action Buttons for Delivered Tab: View

[edit] Authorize CT records

[a] Planner may authorize records by setting a status: Approve, Hold or Reject.

[b] This would be for the entire quantity entered. If CT may be approved with another quantity then:

• planner should reject this CT
• planner should notify shipper about this situation
• shipper should create another CT with new quantity (clone CT feature might be used to speed up this)

[c] Every time status is changed system will:

• request Planner to post comment except for setting "Approve" Status; feature allows the planner to note “why” this shipment was placed on hold (this is for the suppliers benefit as well).

• comment will be recorded in the authorization status history

• send a status notification to the supplier

[d] Shipment(s) that is approved by a planner must effect CT's Authorized fields on General Tab on Internal App as below:

• Authorized by: planner name
• Authorized on: Approved on date
• Authorized MOT: Truck

[edit] Approve Status

[a] This status indicates that the CT is approved to ship immediately.

[b] This status cannot be changed to any other status.

[c] Once this status is set to a CT, it will show on internal live tab.

[d] Once this status is set to a CT, it will show on the TM shipments page.

[edit] Reject Status

[a] This status indicates that the CT cannot ship.

[b] This status cannot be changed to any other status.

[edit] Hold Without Approved For Pick Up On Date Status

[a] This status indicates that the decision has been postponed.

[b] This status can be changed to Reject, Approve or Hold with a date status.

[edit] Hold With Approved For Pick Up On Date Status

[a] This status indicates that CT will be in Hold status until "Approved for Pick Up On:" date. On that date Status will automatically change to Approved Status.

• CT record that has an "Approved for pick up on" date, will show on the internal live tab, TDS, TMS & quick link 72 hours before the current "Approved for pick up on" date set by planner.

[b] Status can be changed to Approved, Rejected or Hold Without Approved For Pick Up On Date Status

• Reject status cannot be applied to a CT record that has an "Approved for pick up on" date set within 72 hrs. See #Approve for pick up on date constraint for ref

[c] This date maybe changed to another date or cleared as many times as required but is subject to #Approve for pick up on date constraint constraint - see below.

[d] This date is affected Cargo Available date. If the hold with date is set, cargo available date is automatically updated to the same day as the hold with date.

[edit] Approve for pick up on date constraint

• If this date is currently blank then it can be set to today or any day in the future
• If this date is already set then it can be set to any date in the future unless the following is true:
  • currently set date is less than 72 hours in the future. In this case date can not be changed (because this MUST not be changed as Jaguar operator probably set up a truck to pick up product already).
  • Warning message: CT#XXXXXX: This date cannot be changed as the previous date is within 72 hours of today's date

[edit] Core Jaguar Functionality

[edit] CT profile on Internal for CTs created by Shipper

• Jaguar User will see new additional fields (CT and Commodity objects)
  • see details here: Cybertrax 2.1 Client (data dictionary)
  • related use case: Cybertrax_2.1_Client_(use_cases)#Use_Case._Susan_continues_updating_fields_for_an_individual_shipment_record

• add #Constraint on the number of lines in Commodity table in CTs created by Shipper User

[edit] See also

See #Truck Domestic Stats TDS feature. This task due to size and development sequence was defined as a top task.

[edit] Misc Functionality

Number of misc features has been requested.

[edit] Planner comments screen

It should record and display the name of the planner or e.m. with the date and time stamp.

• the comment will be recorded in the authorization status history

[edit] Authorization History

All authorization events must be posted. Something like

.

[edit] Notification feature

E-mail notifications should be sent by system in some cases.

[edit] Receipt for created CT by Shipper

This is an e-mail notification that will be sent back to the supplier who created the CT record(s).

• Note: For the phone number as Pick up location and delivery location example below, it will show when there is any phone number on the address book.

 From: cybertrax@jaguarfreight.com
 Sent: Wednesday, June 16, 2010 3:23 PM
 To: mary@jackel.com <this would be the shipper's e-mail address>
 Subject: Confirmation of New CT Record(s) Created

 You have <bold>CREATED</bold> 3 CT record(s) for PO Issued by: <bold>CEI Holmdel</bold>.  

 Pickup Location: --> <bold>                 Delivery Location: --> <bold> 
 CEI Holmdel                                 Gannet Warehouse.
 2182 Rte 35                                 50 Executive Ave. 
 SHolmdel, NJ 07733                          Edison, NJ 08817
 Phone: xxx.xxx.xxx                          Phone: xxx.xxx.xxx

 CT 11111
 PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  <heading should be bold>
 ---    ---    --    ------------       ----    ----           ---          ---         ---     --        

 <This should be the same information that’s listed on the contents table wording & all>

 CT 11112
 PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  <heading should be bold>
 ---    ---    --    ------------       ----    ----           ---          ---         ---     --        

 <This should be the same information that’s listed on the contents table wording & all>

 CT 11113
 PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  <heading should be bold>
 ---    ---    --    ------------       ----    ----           ---          ---         ---     --        

 <This should be the same information that’s listed on the contents table wording & all>

 These record(s) have been sent to: CEI Holmdel <this is the PO Issued By>

 Please do not reply to this message as it is not an actively monitored e-mail address.--> <bold and Italic>

 
 Kind regards,
 EA USA Domestic Team
 at
 Jaguar Freight Services
 10 Fifth Street 3rd floor
 Valley Stream, NY 11581
 Tel:  +1 516-239-1900
 Fax: +1 516-239-6300
 www.jaguarfreight.com
 
 Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
 Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available 
 upon request. 

[edit] Planner Notification Emails

[edit] Status notification Approved

See: #Notification_when_trucker_assigned_by_Jaguar

[edit] Status notification Reject without a comment

Once a planner or external manufacture rejects a CT record, a status notification will be sent back to the shipper who created the CT record.

See example below:

 From: maryanne@cosmeticessence.com <this is the EM or planner who rejected the CT> 
 Sent: Friday, April 30, 2010 5:44 PM
 To: mary@jackel.com <this is the shipper who created the CT records>
 Subject: Rejection Notification for CT 11113

 Dear Mary <this is the shipper who created the CT records>,
 
 The following shipment has been <bold>REJECTED</bold> as per the details below.

 Status		Comment			Last Update		Updated By  --> <this heading should be bold>
 xxxxxx 	                        xx/xx/xxxx   xx:xx           xxxxx

 <this information comes from the history log, last entry>

 Pickup Location:-> <bold>                 Delivery Location: -> <bold>
 CEI Holmdel                               Gannet Warehouse
 2182 Rte 35 S                             50 Executive Ave 
 Holmdel, NJ 07733                         Edison, NJ 08817
 Phone: xxx.xxx.xxx                        Phone: xxx.xxx.xxx

 CT 11113
 PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  <heading should be bold>
 ---    ---   --    -------             ----    ----           ---         ---          ---     --

 <This should be the same information that’s listed on the contents table wording & all>

 To view this online in CyberTrax 2.0, please follow this link: CT# 11113 <CT# hyperlink>



 Cyber Trax 2.0 users please follow this link: http://ct.jaguarfreight.com:8080/Shipper/link.html?path=viewShipment=11113  

 Please do not hesitate should you wish to contact me about this.


 Kind Regards,
 MaryAnne <this is the EM or planner who rejected the CT> 

 Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
 Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available upon request.

[edit] Status notification Reject with a comment

Once a planner or external manufacture rejects a CT record & adds a comment, a status notification will be sent back to the shipper who created the CT record.

See example below:

 From: maryanne@cosmeticessence.com <this is the EM or planner who rejected the CT> 
 Sent: Friday, April 30, 2010 5:44 PM
 To: mary@jackel.com <this is the shipper who created the CT records>
 Subject: Rejection Notification for CT 11113

 Dear Mary <this is the shipper who created the CT records>,
 
 The following shipment has been <bold>REJECTED</bold> as per the details below.

 Status		Comment			Last Update		Updated By  --> <this heading should be bold>
 xxxxxx 	xxxxxxxxxxxxxxx         xx/xx/xxxx   xx:xx           xxxxx

 <this information comes from the history log, last entry>

 Pickup Location: -> <bold>                Delivery Location: -> <bold>
 CEI Holmdel                               Gannet Warehouse
 2182 Rte 35 S                             50 Executive Ave 
 Holmdel, NJ 07733                         Edison, NJ 08817
 Phone: xxx.xxx.xxx                        Phone: xxx.xxx.xxx

 CT 11113
 PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  <heading should be bold>
 ---    ---   --    -------             ----    ----           ---         ---          ---     --

 <This should be the same information that’s listed on the contents table wording & all>

 To view this online in CyberTrax 2.0, please follow this link: CT# 11113 <CT# hyperlink>



 Cyber Trax 2.0 users please follow this link: http://ct.jaguarfreight.com:8080/Shipper/link.html?path=viewShipment=11113  

 Please do not hesitate should you wish to contact me about this.


 Kind Regards,
 MaryAnne <this is the EM or planner who rejected the CT> 

 Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
 Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available upon request.

[edit] Status notification Hold without a date

Once a planner or external manufacture puts a CT record on hold, a status notification will be sent back to the shipper who created the CT record.

 From: maryanne@cosmeticessence.com <this is the EM or planner who puts a CT on hold> 
 Sent: Friday, April 30, 2010 5:44 PM
 To: mary@jackel.com <this is the shipper who created the CT records>
 Subject: Hold Notification for CT 11112
 
 Dear Mary <this is the shipper who created the CT records>,
 
 The following shipment has been placed on <bold>HOLD</bold> as per the details below.

 Status		Comment			Last Update		Updated By  <heading should be bold>
 xxxxxx         xxxxxx 		        xx/xx/xxxx   xx:xx      xxxxx

 Pickup Location: <bold>                   Delivery Location: <bold>
 CEI Holmdel                               Gannet Warehouse
 2182 Rte 35 S                             50 Executive Ave 
 Holmdel, NJ 07733                         Edison, NJ 08817
 Phone: xxx.xxx.xxx                        Phone: xxx.xxx.xxx

 CT 11112
 PO     SKU   Qty  Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack --> <heading should be bold>
 ---    ---   --   -------             ----    ----           ---         ---          ---  --

 <This should be the same information that’s listed on the contents table wording & all>
 
 To view this online in CyberTrax 2.0, please follow this link: CT# 11112 <CT#hyperlink>

 Kind Regards,
 MaryAnne <this is the EM or planner who puts a CT on hold> 

 Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
 Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available upon request.

[edit] Status notification Hold with a date

Once a planner or external manufacture puts a CT record on hold and chooses a date, a status notification will be sent back to the shipper who created the CT record.

 From: maryanne@cosmeticessence.com <this is the EM or planner who puts a CT on hold> 
 Sent: Friday, April 30, 2010 5:44 PM
 To: mary@jackel.com <this is the shipper who created the CT records>
 Subject: Hold Notification for CT 11112

 Dear Mary <this is the shipper who created the CT records>,

 The following shipment has been placed on <bold>HOLD</bold> for <xx/xx/xxxx> as per the details below.

 Status		Comment			Last Update		Updated By  
 xxxxxx         xxxxxx 		        xx/xx/xxxx   xx:xx      xxxxx

 Pickup Location:-> <bold>                Delivery Location:-><bold> 
 CEI Holmdel                                  Gannet Warehouse
 2182 Rte 35 S                                 50 Executive Ave 
 Holmdel, NJ 07733                        Edison, NJ 08817
 Phone: xxx.xxx.xxx                        Phone: xxx.xxx.xxx

 CT 11112
 PO     SKU   Qty    Item Description   # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  -> <heading should be bold>
 ---    ---   --     --------             ----    ----           ---         ---          ---  ---

 <This should be the same information that’s listed on the contents table wording & all>

 To view this online in CyberTrax 2.0, please follow this link: CT# 11112 <CT#hyperlink>

 Kind Regards,
 MaryAnne <this is the EM or planner who puts a CT on hold> 

 Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
 Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available upon request.

[edit] Notification when trucker assigned by Jaguar

Send notification to shipper once Jag operator assigns or re-assigns the pickup trucker for a CT that's already been approved by a planner or external manufacture. This status notification will be sent back to the shipper who created the CT record and also send a copy to eadom@jaguarfreight.com

• Hold with a date CT records also should send this notification to the shipper once Jag operator assigns or re-assigns the pickup trucker to that CT record. It also send a copy to eadom@jaguarfreight.com

• Note: For the phone number as Pick up location and delivery location example below, it will show when there is any phone number on the address book.

• Change request - add different terms according to the Pick up & Delivery location
  • If Pickup location CT_bo#Export_Pick_Up = Elizabeth Arden 1751 Blue Hills Drive Roanoke, VA 24012 make freight terms are Pre-Paid
  • If Delivery location CT_bo#Export_Delivery_To = Elizabeth Arden 1751 Blue Hills Drive Roanoke, VA 24012 make freight terms are Pre-Paid
  • All else, leave as Third Party billing to Elizabeth Arden 1751 Blue Hills Drive Roanoke, VA 24012

See Collect example attached to Mantis [3140]

See Pre-Paid example attached to Mantis [3140]

See Third Party example below:

 From: eadom@jaguarfreight.com 
 Sent: Friday, April 30, 2010 5:44 PM
 To: mary@jackel.com <this is the shipper who created the CT records>
 Bcc: eadom@jaguarfreight.com 
 Subject: Dispatch Confirmation for CT 11111

 Dear Mary <this is the shipper who created the CT records>,

 The following shipment has been APPROVED and will be picked up by: Jewels Transportation <this should be the truckers name only and 
 in bold>. Please ensure that our reference - CT # 11111, <this is the record #> & Load # <this is the load # received from TMS> are 
 clearly recorded on your truck bill of lading.

 Pickup Location:-><bold>                 Delivery Location:-><bold>
 CEI Holmdel                              Gannet Warehouse
 2182 Rte 35 S                            50 Executive Ave 
 Holmdel, NJ 07733                        Edison, NJ 08817
 Phone: xxx.xxx.xxx                       Phone: xxx.xxx.xxx


 Pickup Instructions: <If there are pickup instructions, show pls show it.>

 CT 11111
 PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack <heading should be bold>
 ---    ---   --    --------            ----    ----           ---         ---          ---  ---         

 <This should be the same information that’s listed on the contents table wording & all>

 Freight Charges: <bold and underline>
 Third Party Billing to Elizabeth Arden - 1751 Blue Hills Drive - Roanoke, VA 24012 <bold>


 To view this online in CyberTrax 2.0, please follow this link: CT# 11111 <CT#hyperlink>

 Please do not hesitate to contact us for any additional information.
 
 
 Kind regards,
 EA USA Domestic Team
 at
 Jaguar Freight Services
 10 Fifth Street 3rd floor
 Valley Stream, NY 11581
 Tel:  +1 516-239-1900
 Fax: +1 516-239-6300
 www.jaguarfreight.com
 
 Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
 Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available 
 upon request. 

[edit] System Auto-Reject Email Notification

From: cybertrax@jaguarfreigh.com <System e-mail address> 
Sent: Friday, Jan 14, 2011 12.01 AM <Date time sent>
To: mary@jackel.com <this is the shipper who created the CT records>
Subject: Rejection Notification for CT 11113


Dear Mary <this is the shipper who created the CT records>,
 
The following shipment has been REJECTED as per the details below.

Status	       Comment	                                       Last Update                       Updated By  
REJECTED   This shipment has been automatically                14-Jan-2011 12:01 AM EST          System           
           rejected by the system, due to 90 days 
           of inactivity. 
           Please contact the appropriate purchasing
           group for any further information


 Pickup Location:			Delivery Location: 
 CEI Holmdel                              	 	Gannet Warehouse
 2182 Rte 35 S                             	50 Executive Ave 
 Holmdel, NJ 07733                     	Edison, NJ 08817
 Phone: xxx.xxx.xxx                      	Phone: xxx.xxx.xxx

CT 11113
PO     SKU   Qty   Item Description  # Plts    Pkgs on Plts   Loose Pkgs  TTL GW (lb)  Haz  Stack  
---       ---      --      -------                        ----      ----                   ---                 ---                 ---     --

To view this online in CyberTrax 2.0, please follow this link: CT# 11113 <CT# hyperlink>

Please do not reply to this message as it is not an actively monitored e-mail address.

Kind Regards,
EA USA Domestic Team
at
Jaguar Freight Services
10 Fifth Street 3rd floor
Valley Stream, NY 11581
Tel: +1 516-239-1900
Fax: +1 516-239-6300
www.jaguarfreight.com
 
Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.
 
Please note that all business is transacted subject to our general business terms and conditions, a copy of which is available upon request.

[edit] One user with multiple roles feature

[a] It is possible for one person to have more than one "user role". Example: Shipper / Planner, Shipper / Client; Shipper / Planner / Client; etc.

• This feature works with help of combinations of title checkboxes' states of each Profile section.

for example: when the both checkboxes of Shipper and Planner sections are checked, user gets the both Shipper and Planner rights for work in the Client Application.

[b] There are two different approaches to interface in this case:

• option 1) show separate shipments lists depending on role
• option 2) show one shipments list and provide additional filters that would allow user to show:
  • all shipments
  • only shipments user would see in "shipper role"
  • only shipments user would see in "planner role"
  • only shipments user would see in "client role"

[c] For phase 1 it is suggested to take option 1.

[d] System should "hide" the following features for Shipper, Planner, Shipper/Planner roles:

• CT home
• reports
• user profile
• watch list
• where is
• MAWB tracking

[edit] See Also

See #New Pending Address (NPA) Feature. This was defined a top task.

[edit] Creating CT records by cloning feature

Shipper may add CT record "by cloning" (copying) any CT. This feature helps to quickly create new records that are similar to existing. When shipper selects to "clone" a CT record, the information is to copy except the Cargo Available date. This date should default to today's date.

• IE - Today is 04-Aug-10, I go and clone a previous record that was created back on 26-Jul-10...all of this information (Shipper, Pickup Location, Ship To Location, PO Issued By, Pickup Instruction, Commodity Desc, & the content line) stays the same but the Cargo Available Date is now set to 04-Aug-10.

[edit] Admin for PO issued by CT field

• see Cybertrax_2.1_Client_(data_dictionary)#PO_Issued_by
• This is a "standard dropdown Amin"
• This list must be managed in Admin > Transportation (located on separate tab). See PO Issued By
• Example of values: CEI Holmdel, EA Stamford, CEI Roanoke, Kolmar, Kik, Evergreen

[edit] Admin for Trailer Per Load

• This is a "standard dropdown Admin"
• This list must be managed in Admin > Transportation (located on separate tab). See Trailer Per Load
• Apply to this rule: Commodity#Weight_and_Number_of_Plts_validations_to_web_portal_on_commodity_line_item Validation Rule for weight and number of pallets per commodity line

[edit] Search feature on List CTs

• Filter to search each column on each tab

• Number of records on all tabs
• Download to Excel Button
• See Detail for Web_Portal_Search_Line_Download_to_Excel

[edit] History Log

• It is a log history for a field to view any action that has been done for a particular field. These history will record date time that record has been updated, value of the field, and the field has been updated by.
• Similar feature to History_of_Date
• Apply to these fields:

• Pickup Trucker Name
• Estimated PickUp Date
• Actual PickUp Date
• Delivery Trucker
• Estimated Delivery Date
• Actual Delivery Date
• All of the above updates that are made via the TMS, should display on the history log

[edit] Constraint for Archived Tab for Shipper and Planner

• Shipment should move from Delivered Tab to Archived Tab when its shipment actual delivery date pass 180 days.

[edit] Shipment accessibility

• All the shipments that are created new by shippers, put on hold without a date, on hold with a date more than 72 hours, or rejected by planners SHOULD NOT be showing on the internal Trucking Live shipment list. Not allow Jaguar operator to access these shipments on anyhow such as through shipment list, quick link, virtual group and CTs that are listed on the NPA view new requested address. These shipments must not be showing for Jaguar operator to update or edit fields, because these shipments can be rejected by planners which Jaguar operators should not get involved.

[edit] Email confirmation for shipper account created

Dear (shipper's first and last name),



Welcome to Cybertrax™2.0, Jaguar Freight's unique online web portal. Your account has now been created and your personal login details are listed below. Please also find attached a brief user guide to help you easily navigate through the system.


Login Details:

Username:shipper@emailaddress.net

Password:Jaguar1

(juliet - alpha - golf - uniform - alpha - romeo - one)


Kindly note that the above password is case sensitive. Access is via our website: www.jaguarfreight.com.
We look forward to working with you in the future, however if you require anything further in the meantime please do not hesitate to contact our IT help desk at ihelp@jaguarfreight.com.


Best Regards,

Jaguar Freight Services IT Team.


Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.   Please ensure you have appropriate cover for all your domestic and international shipments.
 

Please note that all business is transacted subject to our general business terms and conditions, as indicated on our freight invoices and HB/L, a copy of which is also available upon request.

[edit] Email confirmation for planner account created

Dear (planner's first and last name),



Welcome to Cybertrax™2.0, Jaguar Freight's unique online web portal. Your account has now been created and your personal login details are listed below. Please also find attached a brief user guide to help you easily navigate through the system.


Login Details:

Username:planner@emailaddress.net

Password:Jaguar1

(juliet - alpha - golf - uniform - alpha - romeo - one)


Kindly note that the above password is case sensitive. Access is via our website: www.jaguarfreight.com.
We look forward to working with you in the future, however if you require anything further in the meantime please do not hesitate to contact our IT help desk at ihelp@jaguarfreight.com.


Best Regards,

Jaguar Freight Services IT Team.


Jaguar Freight does not provide cargo marine insurance unless specifically requested and confirmed in writing.   Please ensure you have appropriate cover for all your domestic and international shipments.
 

Please note that all business is transacted subject to our general business terms and conditions, as indicated on our freight invoices and HB/L, a copy of which is also available upon request.

[edit] Support Link

Allow clients who has question(s) about the web portal to email to the right support group of people

• URL link to eadom@jaguarfreight.com
• URL labe: Portal Shipment Support
• Apply for both Shipper and Planner Interface
• See

[edit] Web Portal Search Line Download to Excel

See Download to Excel

[edit] SKU column width and Copy feature

• Field: SKU

• Width of SKU column to show 16 characters
• Provide copy text functionality from shipment list table on Web Portal
  • The width of SKU column will be increased to handle 16 characters, so that user can read the full SKU number without clicking into each CT record. Ability of right click submenu for copy data field can be provided for SKU and PO, so that “Copy” functionality will allow user to copy the text of SKU or PO field and paste it anywhere they want for their convenient.
• See Figure below:

[edit] When 2 planners set ANY Status to the same record at the same time

• Case found: 2 different planners at the same time, set 2 different status to the same CT record. The system replaces the last value set, but does not warn user that someone else set a status to the record as well.

• Solution: Add warning message to advise user to refresh their browser as another user has already set a status.

[edit] Warning Refresh Message

[edit] Automatic Shipment Rejection Function

• System will automatically rejects all the shipments on New Tab that have Created On Date value greater than 90 days compared to today date.
• Rejected shipments will be moved to the Rejected Tab.
• E-mail notification will be sent out to notify the shipper who created the CT record that “This shipment has been automatically rejected by the system, due to 90 days of inactivity. Please contact the appropriate purchasing group for any further information.” See #System_Auto-Reject_Email_Notification
• This status will be recorded on the history log

[edit] Truck Domestic Stats TDS feature

[edit] Core need

This is a feature to help Jaguar know the number of approved, routed and picked up domestic shipments. Including under the approved status, all hold with a date records, that are within 72 hours of the set hold for pick up on date by planner.

[edit] TDS Solution Overview

It was decided to introduce a concept of #Dashboard for the first time with #TDS Dashboard Panel that would help jaguar operator to monitor CT status. In addition interface to see detailed CT list that belongs to particular status is provided. Functionality to filter CTs and update fields provided.

[edit] Dashboard

• Dashboard is a space on the Cybertrax homepage between the header and footer and consists of one or more dashboard panels. The purpose of it is similar to "car dashboard". It gives overview of important business indicators to the user.
• Dashboard panel normally contains important statistical info but it could also be a graph, etc

[edit] Refresh frequency for Dashboard

• Ideally every 30 to 60 seconds, the dashboard panels total number of approved, picked up and routed CT records are updated.

[edit] TDS option in Jag User profile

• Jaguar users are associated with dashboard panels.
• Jaguar users can have more then 1 dashboard panel.
• Dashboard panels may have parameters defined.
• Dashboard panels should be able to expand, collapse and move around for users to manage their own look and feel. (#Phase One)
  • Dashboard panel default to expand (or open)

[edit] TDS Dashboard Panel

• Should list the total number of CTs that are in 1 of the 3 following status categories:
  • approved, but not routed (including the hold with a date records that are set with a date within 72 hours)
  • routed, but not picked up
  • picked, up but not delivered
• Should list the CT_bo#TMSS_field for each record - See #TMSS_on_TDS

• CT's must satisfy these conditions for each status category:

[edit] Approved status

• • Approved on date = set OR
  • Hold with a date within 72 hours is set AND
  • Pick up trucker = empty AND
  • Actual Pick up Date = empty AND
  • Actual Delivery date = empty

[edit] Routed status

! This is #Phase Two

• • Approved on date = set AND
  • Pick up trucker = set AND
  • Actual Pick up Date = empty AND
  • Actual Delivery date = empty

[edit] Picked Up status

! This is #Phase Two

• • Approved on date = set AND
  • Pick up trucker = set AND
  • Actual Pick up Date = set AND
  • Actual Delivery date = empty

• Need option to view each number of CTs by these 3 status categories & by a 7 day time period

[edit] TDS Action Panel

• This is the list of CTs that are approved, routed and picked up
• View CTs by status categories, table definitions see below:

• Columns for Approved Tab:
  • CT Number
  • Approved On (date)
  • Pick up Location
  • City
  • State
  • Delivery Location
  • City
  • State
  • Total Value
  • HU
  • Gross Weight (LB)
  • TMS Status

• Columns for Routed Tab:
  • CT Number
  • Approved On (date)
  • Pick up Location
  • City
  • State
  • Delivery Location
  • City
  • State
  • Total Value
  • HU
  • Gross Weight (LB)
  • Pick up Trucker
  • Estimated Pick up Date
  • TMS Status

• Columns for Picked Up Tab:
  • CT Number
  • Approved On (date)
  • Pick up Location
  • City
  • State
  • Delivery Location
  • City
  • State
  • Total Value
  • HU
  • Gross Weight (LB)
  • Pick up Trucker
  • Estimated Pick up Date
  • Actual Pick up date
  • Delivery Trucker
  • Estimated Delivery Date
  • TMS Status

• Default order: Latest CT on top
• Sortable?: Yes, ascending and descending, throughout all the shipments for all pages
• Search feature: Filter to search all fields on every tab
  • See list of filters:
    • Approved On (date)
    • Pick up Location
    • City
    • State
    • Delivery Location
    • City
    • State
    • Pick up Trucker
    • Delivery Trucker
    • Estimated Pick up Date
    • Actual Pick up date
    • Estimated Delivery Date
  • Note:
    • For all filters: When any filter is selected, check box for that particular filter should be automatically checked.
    • All filters MUST apply result for all tabs

• Update CTs via the virtual group interface, current list of fields available and 1 new field required.

• Current Virtual Group Interface fields:
  • CT_bo#Estimated Export Pick Up Date
  • CT_bo#Actual Pick up Date
  • CT_bo#Estimated Delivery Date
  • CT_bo#Actual Delivery Date
  • CT_bo#Pick up Trucker
  • CT_bo#Delivery Trucker
  • CT_bo#DT Number
  • CT_bo#PT Number
  • Now including upload to TMS option
    • See Update_Fields_for_Virtual_Group#Updated_business_requirements_11.2F2010_as_TM_is_now_used AND #TMS_Upload_on_Virtual_Group

• 1 New Virtual Group Interface field:
  • CT_#Consol_Warehouse

[edit] TMSS on TDS

[edit] TMS Upload on Virtual Group

[edit] New Pending Address (NPA) Feature (Disable for now)

[edit] Core Need

This feature is for a shipper to enter a Pick up Location address and/or a Delivery Location address that currently does not exist in the CT2 address book.

[edit] NPA Dashboard

This is the number of new pending addresses.

[edit] Shipper NPA Process

• Shipper should be able to add a pickup or delivery address if the address is not listed on the address book.

• For Pick up Location, shipper has to click "No" option, the company address will be empty then create new address.
• Shipper can search an address through the list, while shipper is typing, the system will search for the company name, this works the same for both pick up and delivery location
• If there is no requested address on the system, company-city and company address would be empty
• The new address does not exist in the system, shipper can click "Create New Address" button
• "Create New Address" window pops-up appears for shipper to enter address information
  • There are some required fields and optional fields in order to save; all required fields are marked with asterisk (*) - see #Create New Address fields
  • This allow users to create USA and Canadian addresses only for:
    • Ship to Location
    • Pick up Location

• System would check the entered information from a shipper against the address on the address book.

• All together with company name, city, and remark have to be unique in order to allow shipper to create a new address
• Remark is not a required field
• Shipper enters "Company Name, City, and Remark(optional)" and address info then clicks "Ok"
• System will check those 3 fields with the existing company name, city, and remark
  • IF system find an existing Company Name, City, and Remark, THEN system will ask user to use this found address.
    • IF user clicks "Yes" THEN an existing address will be filled in this field.
    • IF user clicks "No" THEN system will allow user to enter new Remark field to make it unique. If so - system will create a new address with Company Name + City + entered new remark.
  • IF system cannot find any match of an existing Company Name, City, and Remark, THEN system will allow user to create this new address, because it is unique.

• IF shipper does not find an existing address on the dropdown list(address is existing on the address book but does not have location defined properly such as it is defined as pick up but not delivery location or vice versa), shipper can try to create it then the system will search and provide a shipper to select the existing address. This case, this address was not created by a shipper, but send a request to Jaguar Superusers to edit this address by setting delivery location(T5) and (T7) for example then approve the requested location by clicking "Approve".
• Address entered information should be displayed inside of the textbox for company- city and textarea for company address.

• New address entered by shipper should go through an "authorization process". This allows for double checking of the full company name, address entered by shipper does not already exist and avoids unnecessary duplication.

• New pending address added will be displayed on the dropdown list for a shipper to select even though it does not pass the authorization by Jaguar Superuser. This prevents shipper to create many new same company address

[edit] Create New Address fields

• Company Name - Required
• City - Required
• Remark: - Optional
• Address 1: - Required
• Address 2: - Optional
• Address 3: - Optional
• Postcode/Zip: - Required
• Country: - Required - This should be limited to USA and Canada ONLY

• County(UK)/Region: - Optional
• State(US): - Required

• Contact Person: - Optional
• Phone #: - Optional
• Fax #: - Optional

[edit] Jag Internal NPA Process

• Once a new pending address has entered, the NPA dashboard will display the number of new addresses that pending "authorization".
• Superuser clicks on the hyper-linked number of new pending addresses, they get the NPA dashboard panel, showing who created it, status for address request, and the company address information which are for them to approve.

• Who created an address: Shipper first and last name
• Status for address request:
  • Created New: New address requested to add into the system
  • Pick Up Location: This address is already existed on the address book but request to be set as Pick up Location as well
  • Delivery Location: This address is already existed on the address book but request to be set as Delivery Location as well
• Company address consists of: Company address, City, State, Zip, Phone#

• There are 2 ways for superusers to approve the new pending address:

• Superuser can set approval by selecting new pending addresses and press "Approve" button
• Superuser can double click on the address or select an address by selecting a checkbox and then clicking on "View" button and press "Approve" button

• New pending address will not be available for Jaguar operator who edit CTs on shipper, consignee, location...etc fields until this new pending address has been approved by a Jaguar Superuser
• New pending address will not be available on "Replace from Address Book" feature, because user should not replace an unapproved address with another unapproved address.
• New pending address will be available on "Replace from Address Book" feature once superuser approves this new pending address.
• View new requested address will also list all the CTs that use this address with planner authorization status, Created on date and created by.
• Allow Show only US and Canadian addresses

Functionality for a Jag internal superuser to approve an address through:

• View Address

• Pop-up window with address info
• also buttons:
  • Prev: This button is for user to view the previous new pending address on the list of new pending address without returning back to the list of addresses view page.
  • Next: This button is for user to view the next new pending address on the list of new pending address without returning back to the list of addresses view page
  • Edit: This button is for user to edit address information before approving a new pending address(Approve). In the case of an existing address that has Delivery Location or Pick Up Location requested to add by a shipper, Superusers have to edit this address and set proper location fields.
    • For example, if the new pending address requested to add Delivery Location(T5) or (T5) and (T7), Superusers have to edit this address to set appropriated locations.
  • Delete: This button displays only when the new pending address does not have any CT(s) referred to or have all reference CT(s)'s status as rejected by a planner.
  • Replace from Address book: This button displays only when the new pending address is created as "new" (not existed in the system)
  • Approve : This button displays for all the new pending address requested. This is for an approval address.

• Approve: This button displays for all the new pending address requested. This is for an approval address.

This will be a process for a Jag internal superuser to review an address.

• First, superuser has to review the address information requested by a shipper by looking at the requested status.
  • If the company address requested status is "Created New", they'll have to check an address information entered by shipper against the existing address on address book to see if its new. If it is, superuser can view and approve by clicking "Approve" button. This address can be deleted if this address is referred to all rejected CT(s) or there is no any CTs referred to.
  • If the company address requested status is "Pick Up Location" or "Delivery Location", they'll have to view and edit an appropriated transportation field(s) before setting an approval.
• Second, they have to approve the new address by clicking on "Approve". System will update the approved address on the CT record accordingly.

• Once Jag superuser approves or updates an address, the address will also become available in the shipper application address book.

• For use case example, pls see: CyberTrax 2.1 Client (Internal use cases)

[edit] SKU to Planner Mapping Feature

[edit] Core requirement

Only EA Stamford planners should have an option to see shipment records for SKU's that they manage. This information will be provided by Arden as an Excel file.

[edit] Functionality Overview

1) Planner's Map:

• periodically operator will manually upload updated #SKU to Planner map

• #SKU to Planner map will be e-mailed on average once a week and should be uploaded into CT2 by Jaguar user manually (see #Upload panel for SKU to Planner map)

• #SKU to Planner map will be rejected if:
  • it has a different format
  • values exceed max size

• The system should update the master list each time a new spreadsheet is uploaded.

2) Planner's Filter:

• #Planner filter will be added

3) SKU Overwrite:

• After the SKU # is entered by a shipper, suggest the item description as per #SKU to Planner map (if found)
  • option 1: alternatively system suggests and auto fills description if a match is found.
  • option 2: shipper to complete description if no match is found.

• post a note to the preview screen: "Some item descriptions have been replaced according to the EA list of SKU numbers"

• users affected: #Group of planers to see Planer filter

4) Additional column:

• Add additional column "Item SKU Description" to the Shipment's List:
  • apply to all user roles
  • see - #Shipment list with Planner filter
  • Implement mouse over description

• Other additional columns are listed on #Basic Information for this feature section of #Double Approval Process Feature

[edit] Group of planers to see Planer filter

Only planers that have "EA Stamford" on their list of "PO issued by" should see #Planner filter as they are a part of a group for the #Double Approval Process Feature.

[edit] SKU to Planner map

This is an Excel file with the following columns: Item SKU; Planner; Item SKU Description & Piece Price.

Please note that data should start on row 6 to get uploaded.

As well as the Item Sku Description is allowed String and symbols and special character such as "$"

See new example on figure below:

[edit] Planner filter

• Drop down filter has to be added to Shipments List (planner role only)

• Values: planner names (this is the list of all unique values in "planner" column in #SKU to Planner map)

• Items entered by a supplier for which there are no matches found on the list, link to a value “NO MATCH FOUND”

• Default state: "ALL" (filter is off - show all values)

• Label: "Planner's name"

• List of planner's names from the drop down should be dynamic according to the list of ALL shipment records on all tabs within the web portal that have PO Issued by: EA Stamford
  • The list of planner's names is a subset of the master list in the database.
  • For example:
    • User uploads new spreadsheet that contains 3 unique SKU numbers that are mapped to 3 planner's names:
      • SKU1 and Item Desc1 to Planner A, SKU2 and Item Desc2 to planner B, and SKU3 and Item Desc3 to planner C.
    • Shipper X created 3 shipment records with PO. Issued by: EA Stamford, with SKU1, SKU2, and SKU5
      • Shipment 11111 with SKU 1 and Item Desc1 (system suggested)
      • Shipment 22222 with SKU 2 and Item Desc2 (system suggested)
      • Shipment 33333 with SKU 5 and Item Desc3 (no match found)
    • Planners that can approve PO Issued By: EA Stamford will be able to see the planner's name filter with the below list in the drop down:
      • ALL
      • Planner A - because shipment 11111 has SKU1
      • Planner B - because shipment 22222 has SKU2
      • NO MATCH FOUND - because shipment 33333 has SKU5
    • Please note that Planner C should not be listed on the drop down list because there are no shipments on all tabs within the web portal for SKU3 mapped to that planner

• See mock up here: #Shipment list with Planner filter

[edit] Upload panel for SKU to Planner map

[edit] Figure 1. SKU to Planner map

[edit] Figure 2. Warning Message for upload a file

[edit] Figure 3. Incorrect format of uploaded file

[edit] Shipment list with Planner filter

[edit] Figure 4. Planner Portal for BASIC PLANNER with Planner's name filter

[edit] Figure 5. Planner Portal for SUPER PLANNER with Planner's name filter

[edit] SKU TO PLANNER UPDATED

• Change to upload CSV file only
• Line and Columns are the same
• Note - there are some SKU that contains E+ symbols - it's incorrect.. BEFORE exporting to csv format, we should CONVERT SKU column to TEXT format INSTEAD of numeric.. It will prevent representing sku values in scientific format, like "xxxE+xxx"

[edit] Double Approval Process Feature

[edit] Core requirement

EA Stamford planners have a different approval process as compared to turn-key planners. This is a two step process for approvals. Shipments that are approved by basic planners will need a final approval by super planners. This is an additional feature that will support the current EA Stamford planners' authorization process.

[edit] Functionality Overview

[edit] Summary

• This feature applies only to planners who use a double approval process. Other planners who can approve the shipments that have P.O issued by other companies except EA Stamford will not use this feature. Turn-key planners use the current authorization functionality NOT this new feature.

• Planner access to this feature has to be specified on planner profile in the admin section of CT.

• This feature has a setting for an admin to turn on/off.

• Specific cases can be found at CyberTrax 2.1 Client (EA Stamford Planners Only)

[edit] Basic Information for this feature

1) User Type

• Basic planner - See #Basic Planners
• Super planner - See #Super Planners
• This can be set on the Planner Profile section which is a part of the Client Profile. See #Profile Setting

2) Shipment List

NEW TAB

• New shipments, shipments that were approved by basic planners and placed on hold by basic planners are located on the New Tab
  • Differentiate these three types of shipments with color flags:
    • New shipments with white flags - these shipments are new and waiting for an approval.
    • Approved shipments with orange flags - these shipments were approved by basic planners and are waiting for the final approval from the super planner.
    • Hold with or without a date shipments with yellow flags - these shipments were placed on hold by basic planners and are waiting for the final approval from the super planner.

• Shipments that were placed on hold with a date and the system automatically approves, will remain on the New Tab.

• Planner's name column is needed for super planner ONLY.

• Piece Price column is needed ONLY for basic planners but NOT super planners.

APPROVED TAB

• Shipments that were approved by super planner(s) are located on the Approved Tab with Green flags.

HOLD TAB

• Shipments that are placed on hold by a super planner appear here and have a yellow flag.

• Basic planner cannot set an approval status to shipments that are placed on hold by a super planner.

REJECTED TAB

• Shipments that are rejected by basic and super planners.

DELIVERED TAB

• No changes from original functionality.

ARCHIVED TAB

• No changes from original functionality.

3) Approval status panel

It will appear on the "NEW TAB"

• Basic planner: Y only for white flagged shipments
• Basic planner: Y only for orange flagged shipments
• Basic planner: Y with for yellow flagged shipments "Approved for Pick Up On:" yellow flag
• Super planner: Y for all shipments (white, orange & yellow flagged shipments)

To appear on the "APPROVED", "DELIVERED", and "ARCHIVED" TABS

• Basic planner: N
• Super planner: N

To appear on the "HOLD TAB"

• Super planner: Y with "Approved for Pick Up On:" date panel

To appear on the "REJECTED TAB"

• Basic planner: N
• Super planner: N

4) View button

• No changes from original functionality

5) Notification

• Notifications should not be sent when a basic planner sets the approval status. It should ONLY be sent when super planner sets the approval status

• ONLY shipments that are approved by a super planner will become LIVE

• Shipments that are placed on hold with a date by a basic planner, will automatically become approved by the system on that date and shown on New Tab with orange flags. These shipments will need a final approval from a super planner.

• Email Notifications that are system generated include:
  • Approved and routed
    • No changes to the current process
  • Hold and Hold with Date notifications
    • From: basic planner who puts a CT on hold
    • To: shipper who created the CT record
  • Rejection Notification
    • From: basic planner who rejects a CT
    • To: shipper who created the CT record

6) Additional column

• Add additional column "Planner's Name" after "Item Description" to the Shipment's List:
  • Apply ONLY to #Super Planners role and on NEW Tab
  • Ability to sort: Y , throughout all the shipments for all pages
  • Provide mouse over full description (planner's name)
  • If this column does not fit on the page, it will be implemented with scrolling from left to right feature
• Remove column "Piece Price" from the Shipment's List:
  • apply ONLY to #Super Planners role and on NEW Tab
• Add additional column "Status" for color flags to the first column of the shipment's List:
  • apply to both #Basic Planner and #Super Planners roles and on NEW and APPROVED Tab
  • If this column does not fit on the page, it will be implemented with scrolling from left to right feature
  • Ability to sort by color: Y , throughout all the shipments for all pages

[edit] Profile Setting

[a] This feature must be turned on for planners who are a part of double approval process.

[b] Visibility is defined through PO issued by and access user level CT fields defined in Planners profile.

[c] See mock up #Planner's role configuration

[edit] Basic Planners

[a] Each planner is able to see and set approval status for their shipments by using #Planner filter. See #SKU to Planner Mapping Feature

[b] Basic planner(s) are able to set an approval status (Approve, Reject, Hold, and Hold with Date) as normal functionality

[c] Basic planner(s) can change/set an approval status to the shipments on New Tab that are already approved, or have an orange flag to (New, Approve, Reject, Hold, and Hold with Date) and have Cargo Due date set to a future date that is at least over 72 hrs from current date.

[d] Basic planner(s) can change/set an approval status to the shipments on New Tab that are already on hold with a date, or have an yellow flag to (New, Approve, Reject, Hold, and Hold with Date).

[e] Basic planner(s) can change/set an approval status to the shipments on New Tab that are already on hold, or have an yellow flag to (New, Approve, Reject, Hold, and Hold with Date).

[edit] Super Planners

[a] Each planner is able to see and set approval status, to any shipments by using #Planner filter. See #SKU to Planner Mapping Feature

[b] Super planner(s) are also able to approve the shipments that have an orange or white or yellow flag (all shipments are found on the New Tab)

[c] Super planner(s) are able to set an approval status to (Approve, Reject, Hold, and Hold with date) as normal functionality

[edit] Misc Functionality

• SKU to Planner Mapping will ONLY affect new shipments once the master list is updated. It will not affect the shipments that were created before the master list is updated.

• All actions for setting approval status for both basic and super planners should be logged on the History log

[edit] Planner's role configuration

[edit] Figure 1. Example of basic planner configuration user profile

[edit] Figure 2. Example of super planner configuration user profile

[edit] SOW 1

Mantis 3382

Core Requirements:

• Change the auto reject # of days property from hard coded (90 days) to an editable field that Admin Users may edit and maintain.
  • Name "editable field" - Automatically reject shipments on New tab after NNN days of inactivity"

See #Automatic Shipment Rejection Function

[edit] History

[edit] 0002467: [EDI to TMS] (Misc) TDS functionality for TMS

[edit] 0002290: [Client 2.2] Shipper/Planner functionality (phase 2) - TDS Changes

• Virtual Group changes

[edit] 0002559: TDS date fetching refactoring

• Bug/Chng to TDS, Kostya had to implement dates distibution thru Calendar class, not Date

[edit] 0002480: [EDI to TMS] chg: add TMSS column to other tabs: Routed, Picked Up

[edit] 0002567: [EDI to TMS] Shipment(s) that is updated by TM does not save the updated date on date field and on history on Web portal

[edit] 0002531: Add link for web portal support inside the portal for client to email to the right group of people

• 2531
• See Support Link
• Spec is updated: Yes

[edit] 0002485: [ClientSP ph3] Option to download portal records on all tabs into an xls format with some sort of filters

• 2485 See attached file on the mantis
• Spec is updated: Yes

[edit] 0002622: [EDI to TMS ph2] Disable Approved CT Record sent to TMS message for planner role on client app

[edit] 0002986: [EDI to TMS] Change: Add Load# to E-mail dispatch notification sent to shipper user for planner approved CT when load plan rcvd

• Spec is updated: Yes

[edit] 0002638: Increase width SKU column to show 16 characters and provide copy text functionality from shipment list table on Web Portal

• Spec is updated: Yes

[edit] 0002642: Allow basic planner to "unapprove" an item or be able to reject something that they had approved.

• Spec is updated: Yes

[edit] 0002643: Hold status by Basic planner should stay on New Tab with a color coded

• Spec is updated: Yes

[edit] 0002669: Automated shipment rejection for new shipments that has been created more than 30 days<proj>

• Spec is updated: Yes

[edit] 0003208: [EA - Enhancement (Truck-Dom)] Change: Don't allow Rejct Status for Hold w/ Approved for CTs that are w/in 72 hrs of set date

• Spec is updated: Yes

[edit] 0003372: Change: Automated Shipment Rejection Feature - change hard coded # of days from 30 to 90

This change will be implemented in Jan 2012 release

• Spec is updated: Yes