Cargo Due Date Feature

From UG

Revision as of 19:20, 17 May 2011 by Denise (Talk | contribs)
Jump to: navigation, search


Contents

Info

Related mantis:

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

Glossary

Requirements

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.

BR

This feature is for Non Jag users that have role, Planner set in their non jag user profile.

Do we need to set a specific time (number of days) for when this date cannot be changed? IE as like with the hold with a date, date, not upto 72 hrs? Can the Approved for date be = to the due date?

Add Datebox to client app planner role

Display Datebox for planner role when user:

  • Sets the [[]]

Or

  • Sets the [[]]

If/when a shipment is placed on hold without a “approved for” date – then no due date is required, however, when that same shipment is “approved” or status changed to “hold for …/../..” then the “due date” becomes mandatory.

Need to display these results in the CT record on client app for shipper, planner, client roles & internal app on Gen Tab CT_bo#Cargo_due.

Can any planner change this date or just super planners & those who are not subject to the double approval process?

How often can this date change or is it likened to the Hold with a date feature where date cannot be changed 72 hrs before the set date?

KPI Reporting will be required to report/analyze on

  • Created date to approval date
  • Approval date to due date
  • Actual delivery date vs due date (on time performance, variations etc) (this one is an internal requirement EA did not request it

but it has significant value)

Personal tools