Cargo Due Date Feature

From UG

(Difference between revisions)
Jump to: navigation, search
(Functionality)
(Requirements)
Line 27: Line 27:
*The Cargo Due Date set, needs to be displayed:
*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]]
+
**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   
**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 [http://ct.jaguarfreight.com/mantis/view.php?id=2229 2229])
*This date needs to be sent to the TMS on the Shipment Import File. (xml mapping, see Data Dic mapping here [http://ct.jaguarfreight.com/mantis/view.php?id=2229 2229])
Line 37: Line 38:
*This date will also be required for KPI reporting/analysis.
*This date will also be required for KPI reporting/analysis.
-
 
-
*This Date also needs to be displayed on [[Cybertrax_2.1_Client_(requirements)#Truck_Domestic_Stats_TDS_feature]]
 
*This Date also needs to be included into the [[Web_Portal_Search_Line_Download_to_Excel]] list of output
*This Date also needs to be included into the [[Web_Portal_Search_Line_Download_to_Excel]] list of output

Revision as of 20:35, 6 June 2011


Contents

Info

Related mantis:

  • 0002539: [OSDS] ..... <proj>
  • 0002896: [Truck Optimization] ...... <proj>
  • 0002489: [KPI] (External KPIs) Implement phase 1

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 basic planner role, 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 super planner role, this date field is not mandatory to be completed.
  • This date needs to be sent to the TMS on the Shipment Import File. (xml mapping, see Data Dic mapping here 2229)
  • 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.

Functionality

  • Provide option to turn on/off the Cargo Due Date Field on each planner role.
  • This cargo due date field is a Datebox

Cybertrax_2.1_Client_(requirements)#Hold_With_Approved_For_Pick_Up_On_Date_Status.

Personal tools