Licence Tour optimisation operational

Optimisation
Title   
 
 
Tour optimisation   
General
Kebab menu (
)
 
 
 
Type 
Menu item 
Explanation   
 
 
 
  
Tour optimisation 
   
 
  
Personal locations 
   
Tour optimisation
1. Start (Location)
2. For each day from the view you came from, a block with the following information is displayed
a. [Picker] Day of week, Date
 
 
 
 
 
 
No action (default for all days <= today) 
Apply customers, do not optimise day (see also Public holiday calendar) 
Optimise (default for all days > today)      
b. Travel time (TimeSpan from until) | Destination (Location, picker see Start/Destination)
c. The data is preloaded from the Working hours and Home address, or if already present in the week also the hotel information (as in 3.0)
d. The sliders are all active by default
e. On the first day the Home address is set by default, unless the previous day ended with a hotel. Then the hotel is set here.
 
 
 
 
 
 
If the first day is a Monday there is usually no previous day, as Sundays are not worked and the Home address is set. However, if I only optimise a single day, e.g. Wednesday, it can happen that the previous day exists and ended with a hotel (as in 3.0)      
f. On all subsequent days "automatically" is set, unless the day ended at a hotel, then the hotel is used.
g. If the slider is set to "No action", the input fields are deactivated.
3. Action button
a. Optimise
 
 
 
 
 
 
Result popup (not shown on success)      
1) Error case (e.g. server not reachable): Corresponding error message is displayed
2) Not all appointments could be optimised
a) Message: "The following customers (x/y) could not be scheduled due to time constraints: * Confirm to remove the customers from the calendar and apply the result."
b) Action button: Apply
Start / Destination
    1. Start
        a. Home address (the Home address is enforced)
        b. Hotel (only if the previous day ended with a hotel stay)
        c. The global locations stored in the backend
        d. The personal locations created in the client
    2. Destination
        a. Automatic (the optimisation uses either the Home address or a hotel here)
        b. Hotel (only if the previous day ended with a hotel stay)
        c. Home address (the Home address is enforced)
        d. The global locations stored in the backend
        e. The personal locations created in the client
    3. Display
        a. Name, Street, Postal code, Location, Country
Personal locations
Functions in the title bar
 
 
 
Icon 
Explanation   
 
 
+ 
 
Creation of a personal location    
Grid
 
 
 
Click 
Swipe 
Views   
 
 
Edit 
 
 
Delete   
 
 
Table
     
Column definition
 
 
 
Name 
Visible 
Sort 
Full text 
Explanation   
 
 
Name 
Visible 
ASC 
Yes 
  
 
Street 
VisibleOnlyLandscape 
 
 
  
 
 
Postal code  
Visible 
 
 
  
 
Location 
Visible 
 
Yes 
  
 
Country 
Visible 
 
 
   
Create / Edit
    1. Action button
        a. Save
    2. Fields
        a. Name
        b. Street
        c. Postal code
        d. Location
        e. Country
Public holiday calendar
If the Public holiday calendar is available and a corresponding ID is stored for the Employee, the entry changes from "optimise" to "Apply customers, do not optimise day" on days where a public holiday exists.
 
FAQ 
  
 
Release