Cargo Due Date Feature

From UG

Info

parent: 0002539: [OSDS] ..... <proj>

Glossary

Business Needs

Core need

This feature would allow for better optimization, by knowing the number of days to put off picking up shipments; to be able to add more pickups, in the future, to maximize the trucks capacity.

Requirements

This date feature should not be hard coded; it should be allowed to be managed in CT2 >> Admin >> Client App Admin - TMS tab, as an option to display or not to display. (This would be to allow for the scalability of our current TMS solution, for us to provide to other client companies.)

This feature is for Non Jag users that have role, Planner set in their non jag user profile - see Cybertrax_2.1_Client_(requirements)#Core_Planner_Functionality.
- If Non Jag user has planner role with Cargo Due Date Field on, AND Double Approval Process = basic planner, this date field is mandatory and must be completed .
- Also, the system should prevent non jag users with basic planner role from changing the Cargo Due Date set by super planner.
- If Non Jag user has planner role with Cargo Due Date Field on, And Double Approval Process = super planner role, this date field is also mandatory and must be completed. But they also can confirm the date that was already set by basic planner, by approving and/or placing on hold with an approved for pickup date. They do not need to reset the date value, unless its in the past.

The Cargo Due Date set, needs to be displayed:
- CT record, internal application, already has this field on the Gen Tab CT_bo#Cargo_due
- Logged into history - internal CT record updates log & portal shipper/planner history view
- Internal truck domestic stats Cybertrax_2.1_Client_(requirements)#Truck_Domestic_Stats_TDS_feature

This date needs to be sent to the TMS on the Shipment Import File. (xml mapping, see Data Dic mapping here 2229)

Date can be changed often, it is the same functionality as: Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status

Allow the Approved for date to the same as the cargo due date, but it cannot be in the past.

This date will also be required for KPI reporting/analysis.
- Avg Time KPIs

This Date also needs to be included into the Web_Portal_Search_Line_Download_to_Excel list of output

Functionality

Provide option to turn on/off the Cargo Due Date Field on each planner role.

This cargo due date field is a Datebox

If non jag user who has planner role with Cargo Due Date field on, then show this field when planner sets approval status to:
- Cybertrax_2.1_Client_(requirements)#Approve_Status OR
- Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status

Do not display if/when user sets: Cybertrax_2.1_Client_(requirements)#Hold_Without_Approved_For_Pick_Up_On_Date_Status

Display when the status is changed to Cybertrax_2.1_Client_(requirements)#Approve_Status OR

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status.

System should only allow the cargo due date to be = or > than the CT_bo#Cargo_available & CT_bo#Approved_For_Delivery_By_Date & CT_bo#Approved_On

Solution Provided

Summary

Cargo Due Date feature is entered to allow better optimization of truck utilization. It is a last possible date of shipment delivery and allows to Jaguar operator to know how long can be delayed shipment.

It is "PO issued by" specific. Showing the Cargo Due Date is an option for every "PO issued by" and can be managed from Admin section. It can be switched on/off only for double approval CT process which implies approving from Regular Planner and SuperPlanner. For single approval the showing of Cargo Due is not needed.

Admin part

"PO issued by" management panel

"PO issued by" admin section contains a list of Companies that considered as "PO issued by".

For every "PO Issued by" can be set type of approval process (single or double).
For every company with double approving "Cargo Due Date" feature can be switched on/off.
- 8/24 Change = Add On/Off switch for "Cargo Due Date" feature for single approval process planner users

Click to set Double Approval Status

Click to set Single Approval Status

Click to set Cargo Due Date for Double Approval

Where and when to add Cargo due datebox

Planner is a such user that can work with Cargo Due Date feature. So Non-Jaguar user should get Planner role and also should have a list of selected "PO Issued By". Planner can be assigned as Super Planner for "PO issued by" with double approval process.

Please note that check box will be unchecked and read only (grayed out) if "PO issued by" is associated with "Single approval" process.

Super Planner Role

Basic Planner Role

Client part

Add field at the point of setting status (planner user)

Cargo Due Date must be set during approval CT process which can be performed through:

change CT status from any status to Approve status
change CT status from any status to Hold with Approved for Pick Up On Date status

Becomes Read only for Basic planer after Super updated

Must be in Log

Individual CT records updates log

Shipper/Planner History log

Must appear on reports and xls download

xls downl for list CTs, planner role
KPIs (future)
anything else? - Yes
- In Transit Report - Add to list of Output
- Main Report - Add to list of Output
- TDS http://ct.jaguarfreight.com/internal/Index.zul#reportsTDSForm (as filters/columns)? - Both filters & columns
  - Filters - add Date range for Cargo Due
  - Columns - Add Header named Due Date, place in between "Appr on Date" & "Pickup Location". List on ALL 3 Tabs (Approved, Routed & Picked Up) with the date values set by planner user, if no value, leave blank

Date range validation

x? < date < y?

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status

When super planner sets status to basic planner records that has Cargo Due Date values set

There are two different ways for planners to set a status for a CT record and the system must consider them both to allow.

Super Planner to set status: “Approved” for an already Approved Basic Planner CT record, that has the Due Date Set in the “72 hr window” Allow super planner to continue or change/reset the "Cargo Due Date” to a current future date

Super Planner sets status: “Approved” for an already Approved Basic Planner CT record that has the Due Date Set in the past Make super planner change & reset the "Cargo Due Date” to a current future date

Super Planner sets status: “Approved” for an already Approved Basic Planner CT record that has the Due Date Set in current / future Allow super planner to keep the current date value set by basic planner or replace to a current future date, tab view

Allow super planner to keep the current date value set by basic planner or replace to a current future date, record view

When super planner sets status for record without Cargo Due Date

Super Planner sets status: “Approved” for a new record, that does not have a Cargo Due Date set Not allow the user to proceed, CT view

Not allow the user to proceed, Tab view

This date Must visible / editable on appropriate CT details panels

Read only:

Client role, (?) Not yet approved for client role
Shipper role - on CT Shipment View (see IE below)
Planner role - On CT Shipment Vie (see IE below)

Editable:

operator role (internal) (until CT has load assigned)
basic planner (until status set to Approved or date is changed by Super)
super planner (until status set to Approved)

Integration with Descartes

Earliest & Latest Delivery Date = Cargo due date with time window from 9am to 5pm.
- There is no need to increase the # of days to this date as it is a date that says that cargo cannot be delivered any later than that date set.

The TMS will consider the latest delivery date when creating the load and use that as the estimated delivery date for cargo.

It is ok to deliver before the Cargo Due Date it is NOT ok deliver after the cargo due date.

Cargo due date sent to TMS

History

0002295 [TMS (OSDS)] (Cargo Due Date) Add this feature & date fields to CT2 internal & client app shipper/planner view

WU? YES --Denise 12:46, 23 August 2011 (EDT); completed --Denise 12:56, 23 September 2011 (EDT)

0003002 [TMS (OSDS)] (Cargo Due Date) Add cargo due date to shipment import under xml attribute EarliestDelDate & LatestDelDate

WU? Yes

3150: [TMS (OSDS)] (Cargo Due Date) Change: Add Due Date checkbox for planer users who have single approval process

WU? YES - completed --Denise 12:56, 23 September 2011 (EDT)