Cargo Due Date Feature
From UG
(→Business Requirements) |
(→Requirements) |
||
| Line 15: | Line 15: | ||
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. | 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 manage in CT2 >> Admin >> Client App Admin - TMS tab. 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]]. | 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]]. | ||
| Line 34: | Line 36: | ||
* internal app Gen Tab [[CT_bo#Cargo_due]] | * internal app Gen Tab [[CT_bo#Cargo_due]] | ||
| - | Do we need to set a specific time (number of days) for when this date cannot be changed? | + | Some questions asked to take into consideration: |
| + | |||
| + | Do we need to set a specific time (number of days) for when this date cannot be changed? No, but it should be like the hold with a date, where the date cannot be changed 72 hrs before the set date | ||
| - | Can the Approved for date be = to the due date? | + | Can the Approved for date be = to the due date? Y |
| - | Can any planner change this date or just super planners & those who are not subject to the double approval process? Y, same functionality | + | Can any planner change this date or just super planners & those who are not subject to the double approval process? Y, keep the same functionality |
| - | 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? | + | 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? Yes its the same functionality as the Hold with a date feature, where it cannot be changed 72 hrs before the set date |
== KPI Reporting will be required to report/analyze on == | == KPI Reporting will be required to report/analyze on == | ||
Revision as of 20:20, 17 May 2011
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.
Requirements
This date feature should not be hard coded; it should be allowed to manage in CT2 >> Admin >> Client App Admin - TMS tab. 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.
Add/Display a Datebox to client app planner role for when user sets:
- 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
- no due date is required, but 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 then the “due date” becomes mandatory.
Need to display the Cargo Due results in the CT record on:
- client app shipper role
- client app planner role
- client app client role
- internal app Gen Tab CT_bo#Cargo_due
Some questions asked to take into consideration:
Do we need to set a specific time (number of days) for when this date cannot be changed? No, but it should be like the hold with a date, where the date cannot be changed 72 hrs before the set date
Can the Approved for date be = to the due date? Y
Can any planner change this date or just super planners & those who are not subject to the double approval process? Y, keep the same functionality
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? Yes its the same functionality as the Hold with a date feature, where it 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)
