Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Estimating the workload across work groups

Updated on May 25, 2021

Control how Pega Robot Manager anticipates workload across work groups by adjusting the Auto-balancing evaluation interval.

Robotic assignments have a service-level agreement (SLA) deadline. The deadline determines the time by which a robot must complete an assignment. By analyzing the number of assignments that will reach their deadlines during a specific period in the future, Robot Manager can predict the expected workload in a work group.

To achieve that, Robot Manager uses a time window that consists of three auto-balancing evaluation intervals. The default value of an auto-balancing evaluation interval is 60 minutes. For example, when Robot Manager decides whether to move robots between work groups at 8 AM, it looks at how many assignments will reach the SLA deadline between 8 AM and 9 AM, 8 AM and 10 AM, and 8 AM and 11 AM across work groups.

By looking at three subsequent evaluation intervals, the auto-balancing engine determines how the workload in a work group is trending and calculates the number of robots that are needed to complete work on time.

Considerations for adjusting the auto-balancing evaluation interval

Consider the following factors when determining the optimal look-ahead period value to meet your business objectives.

Adjust the auto-balancing evaluation interval carefully

Increasing or decreasing of the auto-balancing interval might affect your robotic workforce in different ways.

The optimal value of the look-ahead period (three times the auto-balancing interval value) must correspond to the service-level agreement (SLA) of your assignments. That is, the SLA of your assignments should match or be slightly less than your look-ahead period.

By decreasing the interval too much, you might unnecessarily increase the number of move, start, or stop operations because the auto-balancing engine might not have enough time to gradually respond to changes in workload.

By increasing the interval too much, the assignments with short service-level agreement deadlines might cause too much randomness in the system.

Consider scheduling robots when using tight SLA deadlines

To prevent robots from moving between work groups too often, do not configure the Auto-balancing evaluation interval to less than 30 minutes, which, multiplied by three, is the value that matches the minimum recommended SLA (1.5 hrs). If you need to configure the SLA in a work group to less than the minimum recommended value, then, in addition to auto-balancing, consider scheduling robots to work within the work group. This way you ensure that the work group has robots available to complete any open assignments at all times.

Consider that auto-balancing engine might ignore the work outside the time period for workload evaluation

Consider an example of a work group that has no robots assigned and has some queued open assignments whose SLA expires in four hours. In this example, the look-ahead period is three hours. In this configuration, the auto-balancing engine will not move a robot to this work group for another hour.

Adjusting the time window for estimating the workload across work groups

Influence the way Pega Robot Manager estimates workload across work groups by adjusting the time period for analyzing open assignments based on service-level agreement.

  1. In the navigation pane of Pega Robot Manager, click SettingsConfigurations.
  2. Expand the Intervals section.
  3. Click the More icon and then select Edit.
  4. Modify the value in the Auto-balancing evaluation interval field according to your business needs.
  5. Confirm your settings by clicking Save.
What to do next: View the analytical dashboards data to understand how Robot Manager balances workload across work groups. For more information, see Analyzing auto-balancing data.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us