Administration - Optimisation settings

Basic principles

In the Administration tab in Opti-Time for Salesforce, the Administrator user can configure the Opti-Time for Salesforce application and define default optimization parameters.

The Optimization parameters for Opti-Time for Salesforce Administration define routes and search around operations that are applied by default.   

Utilisation

> ADMINISTRATION tab > OPTIMIZATION PARAMETERS tab

In the Optimization Parameters tab you can define a series of default parameters for route optimizations or search around events.

The parameters break down into five groups, depending on whether they are: 

  • General parameters
  • Objects to visit parameters
  • Human resources parameters
  • Batch jobs list
  • Fields to display in the list of accounts to optimize

General parameters

- Number of results by default for a search around operation

This parameter defines the number of results by default displayed at the end of a search around. It should be entered in the form of an integer. For example, for a value set to 10, the search around will suggest by default, searching for the 10 nearest objects. 

 This parameter applies to the Opti-time tab > Search around tab, and to a search around executed from the infobox of an object. 

- Save Journeys events in the Salesforce plannings

This parameter adds Journey events into plannings following a geoscheduling operation.

This optimization parameter is only operational in the TOUR and OPTIM versions of Opti-Time for Salesforce.

- Using OT Solver (beta)

This parameter allows you to create user profiles, and then attribute work time and unplanned visit costs to each of them: these may vary from unimportant, (cost set to 0) to very important (cost x10). This means geoplanning teams can take this forward to juggle priorities and ensure these parameters are respected.

This optimization parameter is only functional in the OPTIM version of Opti-Time for Salesforce.

When you have finished defining or modifying the optimization parameters, click on Save at the top right of the screen.


Objects to visit parameters

- An account can be assigned to:

  • A single user (account owner)
  • Many users (a team of accounts)

This configuration will be used for teams of accounts when the Many users option is chosen. It will then be possible to assign values for the parameters of objects to visit as appropriate for the various predefined roles (times and schedules for different accounts depending on the different roles, specific visit days for certain roles…).

This configuration is only available if the account team has been activated in Salesforce beforehand (cf How to configure an account team)

This configuration only applies to the Geoscheduling and Sectorization tabs

Optimization parameters relating to objects to visit are as follows:

- Earliest route start time

This parameter defines the earliest time for the start of a route. It must be entered in the format HH:MM.

This parameter is applied in the Opti-time tab, and then the Optimise a route tab.

- Latest route end time  

This parameter defines the latest time a route may be completed. It must be entered in the format HH:MM.

This parameter is applied in the Opti-time tab > and the Optimise tab, a route.

- Default appointment duration (in minutes)

This parameter defines the default duration of an appointment, expressed in minutes.

This parameter is applied in the Opti-time tab > and the Optimise a route tab.  

- Default unit for frequency

This parameter defines the units (month, day, week) for the chosen frequency.

- Mapping for the frequency field

This parameter allows you to select a field of objects so you can fill their frequency field used at the time of Geoscheduling.

- Apply to all

This parameter, when checked, allows you to fill the fields (times and durations of appointments or visits) with values that have been pre-recorded for all objects (accounts, contacts, leads)

- Sliding time allowed for time windows (in minutes)

This parameter defines the duration for a slipping interval authorised for time windows allocated for visiting accounts or customers, expressed in minutes.   

This optimization parameter is only operational in the TOUR and OPTIM versions of Opti-Time for Salesforce.

When you have finished defining or modifying the optimization parameters, click on Save at the top right of the screen.


Human resources parameters

Optimization parameters relating to resources are as follows:

- Lunch break start

This parameter defines the start time for the lunch break. It must be entered using the following format: HH:MM.

 These parameters relate to the tab Resources > Resource infos > Week.

- End of the lunch break

This parameter defines the lunch break finish time. It must be entered using the format HH:MM.

 These parameters relate to the tab Resources > Resource infos > Week.

- Default duration for the lunch break (in minutes) 

This parameter defines the default lunch break duration in minutes. This duration will be inserted in the lunch time-window defined by the two preceding parameters.  

 These parameters relate to the tab Resources > Resource infos > Week.

- Filter human resources according to role hierarchies

This parameter enables activation of predefined user hierarchies in Salesforce. In the Geoscheduling tab in this case only those users that appear hierarchically below the current user will be suggested as candidates for optimization.

This parameter applies to the Geoscheduling tab > Defining a perimeter

- Allow human resources to validate optimization results

This parameter provides sales forces (users of Salesforce) with access to the history and to optimization summaries so they can accept/refuse geoscheduling results, partially or in their totality.

This parameter is applied to the Geoscheduling tab > History

When you have finished defining or modifying the optimization parameters, click on Save at the top right of the screen.   

More help...

Consult Opti-Time for Salesforce Help to find out how to:


Back to Opti-Time for Salesforce Help