Performance

Every change to a task being committed by a planner results in a request to the Microsoft 365 connector. Moving a task from one Field Worker to another Field Worker will result in two requests, one for removing the entry from the calendar of the first Field Worker and one for adding the task to the calendar of the second Field Worker. Hence, the total number of requests per day is of an order of magnitude determined by the number of Field Workers multiplied by the average number of tasks per Field Worker per day.

Example

Suppose your environment has to deal with about 200 Field Workers, each of them performing around 7 tasks a day on average. The number of tasks in that case would be roughly 200 x 7 = 1,400 tasks / day. In a normal scenario, each task is re-planned about 5-6 times before being closed. Hence, an average scenario with 200 Field Workers would result in 1,400 x 6 = 8,400 requests / day, which is an average of 15 requests / minute based on a 9 hours working day, or 0.075 requests / resource / minute.

To avoid congestion at peek times, OMD uses an exponential backoff algorithm whenever the service is unable to process the requests. The exponential backoff is stopped when it exceeds 15 minutes.