1. Using Capacity Service
  2. Configure Quota Options

Configure Quota Options

Quota configuration helps optimizing the allocation of resources by controlling the availability of mobile workers within defined parameters. Quota configuration provides flexibility in assigning activities to available resources, with different configuration options depending on whether booking is based on direct assignment or quota management. Further, by using quotas, the service activities are booked as per the specified criteria such as time intervals or time slots.

  1. Select Quota from the navigation menu.
  2. Expand capacity area and select a bucket.
  3. Click the Configuration Configuration icon for Capacity. icon.
    The Configuration page for the selected bucket displays.
  4. Select a Booking option:
    • Use Direct Assignment: Specifies that the activities are booked directly on mobile workers' routes. If you've configured a capacity area for booking using direct assignment, the activity is created (or reassigned) in a mobile worker’s route. The activity is created, only if the mobile worker meets the activity requirements and has enough time to complete it.
    • Use Quota Management > Based on Booking Intervals: Specifies that the activities are booked based on the booking intervals selected on this page. When you select this option, the activity is created on a bucket that's associated with the capacity area.
    • Use Quota Management > Based on Time Slots: Specifies that the activities are booked based on the selected time slots. When you select this option, the activity is created on a bucket that's associated with the capacity area.

      For more information, see the Activity Booking section.

  5. Select the configuration options displayed based on the booking option that you selected and click Save.
    Parameter Options
    Use Direct Assignment
    Booking

    • Show recommendations in activity booking screen

      Defines whether you want to show the booking recommendations. When you select this check-box, the Book Activity page might show a time slot with a special icon, indicating a recommendation. The recommendation is a time slot that has a bigger probability of decreased overall travel expenses. For more information, see the Booking Recommendations topic.

    • Optimization goal

      Allows choosing between Default (early scheduling) or Optimize Travel.

    • Use forecasted activities during booking

      Option to consider forecasted activity flows during booking.

      • Forecast the activity flow within the days range

        Defines the forecast range in days, with minimum and maximum values from 0 to 31. A value of 0 indicates the current day. This option is visible only when the Use forecasted activities during booking option is selected. Choose the forecast range carefully based on operational needs. A broader range improves optimization but might increase processing time.
        • For dates before the range, only routes that already contain activities close to the booking are suggested.
        • For dates within the range, the activity flow forecast is applied in a way that additional travel in the proposed routes is close to the per-bucket average.
        • For dates after the range ends, all the feasible route positions are returned.

    • Time slots

      Defines the time-slots during which resources can book activities.
      Note: The list is automatically synchronized between the connected capacity area and capacity area using the Resource Info page.
    When you select Use forecasted activities during booking, the scheduling options returned would be different from the default settings. The behavior of returned schedule options varies based on the date range as follows:
    • Dates Before the Minimum Day of the Range:
      • Returned options include routes where:
        • The activity is adjacent to an existing activity on the route.
        • The additional travel caused by adding the activity to the route is under 120% of the average per-bucket travel, suggesting close proximity to existing activities on the route.
      • Additional travel is calculated as the difference in total travel on the route with and without the new activity.
      • Additional travel to and from the given activity is estimated using the airline distance method.
    • Dates Within the Range (from Minimum to Maximum Day):
      • Returned options include routes where:
        • The activity is adjacent to an existing activity with the same travel key.
        • The additional travel caused by adding the activity to the route is under 120% of the average per-bucket travel, suggesting close proximity to existing activities on the route.
        • Options where the average additional travel is less than 120% of the average per-bucket travel suggesting close proximity to forecasted activities on the route.
      • The expected number of activities in the future is determined by multiplying the average number of activities booked per day for the specific travel key by the number of days from today until the scheduled option date.
      • Additional travel To and From the given activity is estimated using airline distance method. To estimate travels between activities in the same travel key, the average travel per travel key is used.
      • Additional travel for forecasted activities is estimated using statistical data. If sufficient data is unavailable, the dates within the range are processed using the same logic as 'Dates Before the Minimum Day of the Range,' meaning no forecasted activities are considered.
      • Additional travel is calculated as follows:
        • First, calculate the total travel distance in the route, including the given activity at the proposed location in the route along with the expected number of activities for the same travel key after the given one.
        • Then, calculate the total travel distance in the route if the given activity is excluded.
        • Subtract the second value (without the given activity) from the first value (with the given activity).
        • Finally, divide this difference by the expected number of activities + 1 (to account for the added activity).
    • Dates After the Maximum Day of the Range
      • All possible route options are returned, following the standard findMatchingResources API behavior without activity flow forecasting.
    For example, in an environment where:
    • Activity flow forecast is enabled by default.
    • Scheduling has a range of 2 to 7 days.
    • Two activities are scheduled with the same travel key - one for Monday and one for Thursday.
    • One mobile worker is available with the required skills.
    • According to historical data:
      • Average activity creation rate for this travel key is 0.75 activities per day over the last 30 days.
      • The travel key is classified as distant, with travel times estimated to be 1.5 times longer than the bucket average.
    • According to travel statistics the average travel per travel key is 0.33 times of the bucket average.
    The activity flow forecast outcome would be as follows:
    • Monday (Day 1)
      • The activity is planned either next to or before the existing activity in the same travel key.
    • Tuesday
      • No options are returned. There are no activities in the route with the same travel key.
    • Wednesday
      • No options are returned. By Wednesday, the system expects two activities to be booked. The average additional travel would exceed by 122% of the average per-bucket travel.
      • Calculation: Additional travel calculation for Wednesday.
      • Substituting Values: Additional travel substituting values for Wednesday.
    • Thursday
      • The activity is planned either next to or before the existing activity in the same travel key.
    • Friday
      • Options fitting four activities in a row are returned.
      • The application expects three activities to be booked. Travel efficiency improves with this forecast, as the additional travel is less than the bucket travel average.
      • Calculation:Additional travel calculation for Friday.
    • Saturday and Sunday
      • Options fitting four activities in a row are returned, as this number of activities provides acceptable travel efficiency.
    • Next Monday and Beyond
      • All options fitting at least one activity are returned.
      • No forecast is applied beyond the configured day range.
    Use Quota Management - Based on Booking Interval
    Booking

    The following options are available:

    • Allow to close booking on work zone level

      Defines whether booking can be closed on a particular work zone level.

    • Show recommendations in activity booking screen

      Defines whether you want to show the booking recommendations. When you select this check-box, the Book Activity page might show a time slot with a special icon, indicating a recommendation. The recommendation is a time slot that has a bigger probability of decreased overall travel expenses.

    • Optimization goal

      Allows choosing between Default (early scheduling) or Optimize Travel.

    • Use forecasted activities during booking

      Option to consider forecasted activity flows during booking.

    • Forecast the activity flow within the days range

      Defines the forecast range in days, with minimum and maximum values from 0 to 31. A value of 0 indicates the current day. This option is visible only when the Use forecasted activities during booking option is selected. Choose the forecast range carefully based on operational needs. A broader range improves optimization but might increase processing time.
      • For dates before the range, only routes that already contain activities close to the booking are suggested.
      • For dates within the range, the activity flow forecast is applied in a way that additional travel in the proposed routes is close to the per-bucket average.
      • For dates after the range ends, all the feasible route positions are returned.

    • Activity starting threshold, %

      Adjust the starting threshold to ensure activities have adequate time buffers and avoid overlaps with other bookings. This works same as LateStartMitigation parameter in the showBookingGrid and activityBookingOptions operations within the Capacity APIs. When the value is greater than 0, the application refrains from suggesting bookings for activities expected to start within the last defined threshold percentage of the time slot duration. This functionality optimizes resource utilization and improves the customer experience by reducing late starts.

    • Booking intervals

      Defines a list of time intervals to be used to manage booking.

      Note:
      • The default values are automatically synchronized with the Business Rules time intervals. You can adjust the values for the individual bucket.
      • During upgrade, if you select available capacity based quota management, then the application migrates to Booking Intervals based quota with either quota in absolute time units or quota in percent of available capacity (depends on the quota by day settings).
      • To change the number of hours per day (used to recalculate working time plans (or number of resources) to Max Available (hours/minutes) or vice versa), navigate to Business Rules page, select "man-days" in the Measurement units for Quota and Available Capacity field and change the value of number of hours per man-day.

    • Override intervals

      This value is used to show Booking status. If no values are defined, the default Capacity intervals configured on Business rules level are used. Allows you to add, modify, or revert to default booking intervals.

    When you select Use forecasted activities during booking, the scheduling options returned would be different from the default settings. The behavior of returned schedule options varies based on the date range as follows:
    • Dates Before the Minimum Day of the Range:
      • Returned options include routes where:
        • The activity is adjacent to an existing activity on the route.
        • The additional travel caused by adding the activity to the route is under 120% of the average per-bucket travel, suggesting close proximity to existing activities on the route.
      • Additional travel is calculated as the difference in total travel on the route with and without the new activity.
      • Additional travel to and from the given activity is estimated using the airline distance method.
    • Dates Within the Range (from Minimum to Maximum Day):
      • Returned options include routes where:
        • The activity is adjacent to an existing activity with the same travel key.
        • The additional travel caused by adding the activity to the route is under 120% of the average per-bucket travel, suggesting close proximity to existing activities on the route.
        • Options where the average additional travel is less than 120% of the average per-bucket travel suggesting close proximity to forecasted activities on the route.
      • The expected number of activities in the future is determined by multiplying the average number of activities booked per day for the specific travel key by the number of days from today until the scheduled option date.
      • Additional travel To and From the given activity is estimated using airline distance method. To estimate travels between activities in the same travel key, the average travel per travel key is used.
      • Additional travel for forecasted activities is estimated using statistical data. If sufficient data is unavailable, the dates within the range are processed using the same logic as 'Dates Before the Minimum Day of the Range,' meaning no forecasted activities are considered.
      • Additional travel is calculated as follows:
        • First, calculate the total travel distance in the route, including the given activity at the proposed location in the route along with the expected number of activities for the same travel key after the given one.
        • Then, calculate the total travel distance in the route if the given activity is excluded.
        • Subtract the second value (without the given activity) from the first value (with the given activity).
        • Finally, divide this difference by the expected number of activities + 1 (to account for the added activity).
    • Dates After the Maximum Day of the Range
      • All possible route options are returned, following the standard findMatchingResources API behavior without activity flow forecasting.
    For example, in an environment where:
    • Activity flow forecast is enabled by default.
    • Scheduling has a range of 2 to 7 days.
    • Two activities are scheduled with the same travel key - one for Monday and one for Thursday.
    • One mobile worker is available with the required skills.
    • According to historical data:
      • Average activity creation rate for this travel key is 0.75 activities per day over the last 30 days.
      • The travel key is classified as distant, with travel times estimated to be 1.5 times longer than the bucket average.
    • According to travel statistics the average travel per travel key is 0.33 times of the bucket average.
    The activity flow forecast outcome would be as follows:
    • Monday (Day 1)
      • The activity is planned either next to or before the existing activity in the same travel key.
    • Tuesday
      • No options are returned. There are no activities in the route with the same travel key.
    • Wednesday
      • No options are returned. By Wednesday, the system expects two activities to be booked. The average additional travel would exceed by 122% of the average per-bucket travel.
      • Calculation: Additional travel calculation for Wednesday.
      • Substituting Values: Additional travel substituting values for Wednesday.
    • Thursday
      • The activity is planned either next to or before the existing activity in the same travel key.
    • Friday
      • Options fitting four activities in a row are returned.
      • The application expects three activities to be booked. Travel efficiency improves with this forecast, as the additional travel is less than the bucket travel average.
      • Calculation:Additional travel calculation for Friday.
    • Saturday and Sunday
      • Options fitting four activities in a row are returned, as this number of activities provides acceptable travel efficiency.
    • Next Monday and Beyond
      • All options fitting at least one activity are returned.
      • No forecast is applied beyond the configured day range.
    Capacity Management

    The following options are available:

    • Capacity categories

      Defines a list of capacity categories that you want to use for the capacity area.
      Note: The list is automatically synchronized between the connected capacity category and capacity area using the Resource Info page.

    • Working time unit

      Select one of the following options to define the column in which you want to display the planned values in the Available Capacity screen:

      • hours: The planned amount of working time is displayed in hours in the Capacity column.

        Note: The Hours, Minutes, or Man-days option displays based on the option selected from the Measurement units for Quota and Available Capacity drop-down list in the Business Rules page.
      • resources: The planned amount of resources are displayed in the Resources column.

    • Start of day travel time is included in the used time

      Select the check-box to include the resource’s first travel time for calculating the Used Quota parameter. The first travel time in a mobile worker route is defined as the time required to travel from the mobile worker's start location to the first activity location.

      Note: By default, the check-box is enabled to maintain backward compatibility with all capacity areas.

    • End of day travel time is included in the used time

      Select the check-box to include the resource’s final travel time for calculating the Used Quota parameter. The final travel time in a mobile worker route is defined as the time required to travel from the mobile worker's final activity location to the mobile worker's end location configured in the application.
    Quota management > Manage quota by day

    Defines how quota is entered by day. The following options are available:

    • Enter quota as % of capacity defined by calendar and then switch to the working time plans

      Allows to use the available capacity for a specified number of days and then switch back to planned capacity. Select the number of days in the For the next days field.

    • Enter quota as % of capacity defined by calendar

      Select this option to use available capacity for booking. This means the application adjusts quota based on the maximum available quota during the day. For example, if a resource is sick, quota is reduced correspondingly.

    • Enter quota as % of working time plans

      Select this option to use planned capacity for booking.

    • Quota is entered in minutes

      Select this option to enter quota values in minutes.

    • Reduce quota by the total duration of activities not assigned to any capacity category

      Select this option to reduce quota by volume of activities not assigned to any capacity category.

      Visible when one of the following options is selected:
      • Enter quota as % of capacity defined by calendar and then switch to the working time plans
      • Enter quota as % of capacity defined by calendar
      • Enter quota as % of working time plans
    Quota management > Manage quota by capacity category

    Defines how quota is entered by capacity category. The following options are available:

    • Quota is entered as % of maximum capacity available in this categoryIf this option is enabled, the quota is defined as % of capacity available by calendar in this capacity

      category.

    • Quota is entered as % of quota defined on parent levelIf this option is enabled, the quota is defined as % of quota defined on the day level.

    • Quota is entered in minutesSelect this option to enter quota values in minutes.
    Quota management > Manage quota on the level of booking intervals
    Ensure that limits are defined for all booking intervals and capacity categories. Otherwise, missing values will be replaced with "zero quota limit", which means that booking is prohibited for such categories and intervals. Visible when one of the following options is selected:
    • Enter quota as % of capacity defined by calendar and then switch to the working time plans
    • Enter quota as % of working time plans
    Use Quota Management - Based on Time Slots
    Booking

    • Allow to close booking on work zone level

      Defines whether booking can be closed on a particular work zone level.

    • Show recommendations in activity booking screen

      Defines whether you want to show the booking recommendations. When you select this check-box, the Book Activity page might show a time slot with a special icon, indicating a recommendation. The recommendation is a time slot that has a bigger probability of decreased overall travel expenses. For more information, see the Booking Recommendations topic.

    • Optimization goal

      Allows choosing between Default (early scheduling) or Optimize Travel.

    • Use forecasted activities during booking

      Option to consider forecasted activity flows during booking.

    • Forecast the activity flow within the days range

      Defines the forecast range in days, with minimum and maximum values from 0 to 31. A value of 0 indicates the current day. This option is visible only when the Use forecasted activities during booking option is selected. Choose the forecast range carefully based on operational needs. A broader range improves optimization but might increase processing time.
      • For dates before the range, only routes that already contain activities close to the booking are suggested.
      • For dates within the range, the activity flow forecast is applied in a way that additional travel in the proposed routes is close to the per-bucket average.
      • For dates after the range ends, all the feasible route positions are returned.

    • Time slots

      Defines the time-slots during which resources can book activities.

      Note: The list is automatically synchronized between the connected capacity area and capacity area using the Resource Info page.
    When you select Use forecasted activities during booking, the scheduling options returned would be different from the default settings. The behavior of returned schedule options varies based on the date range as follows:
    • Dates Before the Minimum Day of the Range:
      • Returned options include routes where:
        • The activity is adjacent to an existing activity on the route.
        • The additional travel caused by adding the activity to the route is under 120% of the average per-bucket travel, suggesting close proximity to existing activities on the route.
      • Additional travel is calculated as the difference in total travel on the route with and without the new activity.
      • Additional travel to and from the given activity is estimated using the airline distance method.
    • Dates Within the Range (from Minimum to Maximum Day):
      • Returned options include routes where:
        • The activity is adjacent to an existing activity with the same travel key.
        • The additional travel caused by adding the activity to the route is under 120% of the average per-bucket travel, suggesting close proximity to existing activities on the route.
        • Options where the average additional travel is less than 120% of the average per-bucket travel suggesting close proximity to forecasted activities on the route.
      • The expected number of activities in the future is determined by multiplying the average number of activities booked per day for the specific travel key by the number of days from today until the scheduled option date.
      • Additional travel To and From the given activity is estimated using airline distance method. To estimate travels between activities in the same travel key, the average travel per travel key is used.
      • Additional travel for forecasted activities is estimated using statistical data. If sufficient data is unavailable, the dates within the range are processed using the same logic as 'Dates Before the Minimum Day of the Range,' meaning no forecasted activities are considered.
      • Additional travel is calculated as follows:
        • First, calculate the total travel distance in the route, including the given activity at the proposed location in the route along with the expected number of activities for the same travel key after the given one.
        • Then, calculate the total travel distance in the route if the given activity is excluded.
        • Subtract the second value (without the given activity) from the first value (with the given activity).
        • Finally, divide this difference by the expected number of activities + 1 (to account for the added activity).
    • Dates After the Maximum Day of the Range
      • All possible route options are returned, following the standard findMatchingResources API behavior without activity flow forecasting.
    For example, in an environment where:
    • Activity flow forecast is enabled by default.
    • Scheduling has a range of 2 to 7 days.
    • Two activities are scheduled with the same travel key - one for Monday and one for Thursday.
    • One mobile worker is available with the required skills.
    • According to historical data:
      • Average activity creation rate for this travel key is 0.75 activities per day over the last 30 days.
      • The travel key is classified as distant, with travel times estimated to be 1.5 times longer than the bucket average.
    • According to travel statistics the average travel per travel key is 0.33 times of the bucket average.
    The activity flow forecast outcome would be as follows:
    • Monday (Day 1)
      • The activity is planned either next to or before the existing activity in the same travel key.
    • Tuesday
      • No options are returned. There are no activities in the route with the same travel key.
    • Wednesday
      • No options are returned. By Wednesday, the system expects two activities to be booked. The average additional travel would exceed by 122% of the average per-bucket travel.
      • Calculation: Additional travel calculation for Wednesday.
      • Substituting Values: Additional travel substituting values for Wednesday.
    • Thursday
      • The activity is planned either next to or before the existing activity in the same travel key.
    • Friday
      • Options fitting four activities in a row are returned.
      • The application expects three activities to be booked. Travel efficiency improves with this forecast, as the additional travel is less than the bucket travel average.
      • Calculation:Additional travel calculation for Friday.
    • Saturday and Sunday
      • Options fitting four activities in a row are returned, as this number of activities provides acceptable travel efficiency.
    • Next Monday and Beyond
      • All options fitting at least one activity are returned.
      • No forecast is applied beyond the configured day range.
    Capacity management

    • Capacity categories

      Defines a list of capacity categories that you want to use for the capacity area (that's, capacity area).

      Note: The list is automatically synchronized between the connected capacity category and capacity area using the Resource Info page.
    • Working time unitSelect one of the following options to define the column in which you want to display the planned values in the Available Capacity screen:

      • hours: The planned amount of working time is displayed in hours in the Capacity column.

        Note: The Hours, Minutes, or Man-days option displays based on the option selected from the Measurement units for Quota and Available Capacity drop-down list in the Business Rules page.

      • resources: The planned amount of resources are displayed in the Resources column.

    • Start of day travel time is included in the Used time

      Select the check-box to include the resource’s first travel time for calculating the Used Quota parameter. The first travel time in a mobile worker route is defined as the time required to travel from the mobile worker's start location to the first activity location.

      Note: By default, the check-box is enabled to maintain backward compatibility with all capacity areas.

    • End of day travel time is included in the Used time

      Select the check-box to include the resource’s final travel time for calculating the Used Quota parameter. The final travel time in a mobile worker route is defined as the time required to travel from the mobile worker's final activity location to the mobile worker's end location configured in the application.
    Quota management > Manage quota by day

    Select this option to use available capacity for booking. This means the application adjusts quota based on the maximum available quota during the day. For example, if a resource is sick, quota is reduced correspondingly.

    When selected the following options become visible:

    • Quota is entered as % of capacity defined by calendar

      If this option is enabled, the quota is defined as % of daily capacity available by calendar.

      When selected the following additional option is displayed:

      • Reduce quota by the total duration of activities not assigned to any capacity category

        Select this option to reduce quota by volume of activities not assigned to any capacity category.

    • Quota is entered in minutes

      If this option is enabled, the quota is defined as a number of minutes available for this day.
    Quota management > Manage Quota by Capacity Category

    When selected the following options become visible:

    • Quota is entered as % of maximum capacity available in this category

      If this option is enabled, the quota is defined as % of quota defined on the day level.

    • Quota is entered as % of quota defined on parent level

      If this option is enabled, the quota is defined as % of quota defined on the day (time slot) level.

      • Estimate quota based on historical data

        This parameter defines whether the application must estimate the '% Quota' values based on the historical data.

        • Historical values to be used

          This parameter defines if the 'Quota %' or 'Used capacity %' values should be processed for the "estimate quota" functionality.

        • Processing historical data period (same weekdays)

          Select One week or One month or Two months to set the length of historical data period to be analyzed.

      • Automatically adjust 'Quota. %' values to keep their total equal to 100%

        This parameter defines if the total sum of the '% Quota' values should always be equal to 100%.

    • Quota is entered in minutes

      If this option is enabled, the quota is defined as a number of minutes available in this category for this day.
    Quota management > Manage Quota by Time Slot

    • Quota is entered as % of capacity available by calendar

      If this option is enabled, the quota is defined as % of time slot capacity calculated by calendar.

    • Quota is entered as % of quota defined on parent level

      If this option is enabled, the quota is defined as % of quota defined on the day level.

    • Quota is entered in minutes

      If this option is enabled, the quota is defined as a number of minutes available for this time slot.