How many tasks can I assign at once to a single user?

When you initially start to use FSM - you may assign a small handful of tasks per person. However, this can quickly get out of control and you might start assigning quantities of tasks that are outside of a realistic realm for someone to actually complete.

BASIC TASK ASSIGNMENT - ASSUMPTIONS

Let’s start with some basic assumptions:

• Assume the average task takes 15 - 20 mins to complete

• Assume the average drive time to get to a task is also about 15 mins

• Assume the average shift length is 12 hours

• This means that an individual task owner can realistically complete about 24 tasks per day.

Even if we cut those timings in half - we get about 48 tasks.

NOTE: These could go up or down slightly given differences in drive times - for example, in the Permian basin, drive times can be much higher, thereby reducing the number of tasks that can be completed.

HOPPER STYLE ASSIGNMENTS - CONSIDERATIONS

However, you may eventually run tasks in a group assignment style format with a hopper of tasks that get assigned to multiple personnel so that they can get done in parallel.

For e.g.

• let’s say you have 4 operators sharing a region.

• Let’s continue to assume each person can do 24-48 tasks per day

• If we group assign the tasks - we would be assigning about 200 tasks per operator per day.

USABILITY WARNING: HOWEVER, note that while the application can handle assigning 200 tasks to each individual - it may not make sense to have an individual user browse through a list of 200 tasks on their mobile app to select which ones they should do.

Recommendation: Ensure your groupings of personnel for field coverage allow for a practical view, review and execution of a realistic quantity of tasks given drive times and task times

MOBILE APP PERFORMANCE

The above recommendations take into consideration practical field realities and usability considerations. The above being said - here are some performance parameters we have noticed on the mobile app along with some high level inputs of

• the actual likelihood of amount of tasks getting done in the field and

• the usability of the information related to the amount of tasks in the field.